Rule not working - due date approaching

[Rashad_Issa]

Hello everyone,

I am facing an issue trying to create a rule to notify assignees and ‘people’ custom field individuals that their task is approaching its deadline.
This is required for a compliance workflow we have.

Here are two sets of rules we tested and neither of them worked.

Can someone please take a look and advise what I have missed from the set up or what I need to change to get the rule to work?

Thanks a mil.

[Phil_Seeman]

Hey @Rashad_Issa,

Does the rule run history, and the task activity, indicate that the rule is not firing at all? (That’s my guess.)

You do know that these rules are only evaluated at midnight, right? And that they’ll only evaluate to true on midnight of the exact specific day(s) that you have in the trigger?

[Rashad_Issa]

Hi @Phil_Seeman

Yes, the rule has not run at all and I am aware of the midnight run time.
The rule was created about 2 months ago and June is when it should have run, but that did not happen.
thats when I replicated it with the intention to run yesterday midnight, and that did not happen as well not sure what to do.

[Phil_Seeman]

Here’s your problem, @Rashad_Issa!

OK, just kidding; I’m sure you paused that rule to test out the second one.

Honestly, I’m as baffled as you are. @lpb @Bastien_Siebman @Richard_Sather etc - any ideas?

[Christine_Bolton]

@Rashad_Issa – have you tested to see if removing check if condition does anything?

[lpb]

I agree with @Christine_Bolton to remove the Check if.

I wouldn’t think that would prevent the rule from firing, but you never know.

And I’m pretty sure it’s redundant; Due date is approaching rules won’t run on completed tasks.

Are you sure you have tasks that qualify?

To test, I’d make a new rule like this (assuming you get this in before midnight tonight):

• Due date is approaching Today
• No Check if
• Add comment “test” (no variable)
• Add a task with a due date of Thursday
• See what happens after 1AM Thursday; if it doesn’t work, send screenshot to Support

Thanks,

Larry

[Arthur_BEGOU]

I had the same issue in a similar rule recently, didn’t find a solution so far.
I’ll try to recreate the trigger as advised

[Rashad_Issa]

Thank you all for your help provide solutions.
Will test and see if the rule works for Monday. I will update you all on here then.
Have a lovely weekend.

[Leigh_Flynn]

Is it possible those tasks are actually subtasks? Whenever I’ve had similar incidents, it always turns out I’d overlooked allowing the rule to run on subtasks. I seem to have trouble remembering to do that since the latest UI update moved that toggle from the main rule editing page to inside the settings menu.

[Rashad_Issa]

Thanks Leigh. Those are def tasks and not subtasks. I know what you mean though, I had encountered that oversight couple of time before

[Bradley_Camm]

Hi all,

I work in Rashad’s team and have tested the rule (removing the ‘check if’ section and ensuring the due dates are correct) and the rule still has not run / hasn’t worked.

Could someone please advise on this issue, thank you!

[Rashad_Issa]

Thanks @Bradley_Camm

@Vanessa_N & @Emily_Roman any ideas if this is normal behaviour of whether it is a bug?

[lpb]

@Rashad_Issa and @Bradley_Camm,

I actually suggested a more simple test to really isolate the issue.

But I think you’ll need Support, which you could do with your current rule. Just include specific links to the project, task(s) that should have changed, and the rule in your request.

Thanks,

Larry

[Jan-Rienk]

It does sound like a possible candidate for English Forum > Critical Bugs , flagging for @Forum-team

[Bradley_Camm]

Hi all,

The rule is now running when removing the ‘check if’ and the assignee notified. Thank you for your advise and support.