Why is my Rule "Waiting" ??

Hi Folks

Lately I’ve noticed when I create a new task that the rule I have set that is triggered by a new task pops up a window saying “Rule Waiting” and you have to navigate away from the task for the rule to run.

This means that if you have set other things in the task that trigger more rules that they don’t run because the first rule hasn’t run yet.

It’s a bit of a pain becuase I now have to name the task, navigate away then come back to it and add dates asignees etc for it to work.

Has anyone else seen this behavour?

Cheers

Shaun

This was created to fix a specific issue: you open a task, start editing the description, fields and title, and your rules run so it messes up with what you wrote. Now, rules are paused, so you can work on the task without being disturbed. OR you can decide to click the “run” button

Haha just my luck.

My workflow relies on the rule running immediatly and this change has screwed up our whole organisation, we are getting things missed all over the place

Can you explain exactly what the workflow is and why it relies on things being things running right away?

Hi
here’s a simplified overview

we have an ongoing project for each department in our company, Market, Customer Service, Warehouse etc for day to day tasks. When assigning tasks to employees it immediatly adds the task to the correct projects

To avoid having to implement the same rules again and again in every project I have another project called Robotman which acts as the Rule Hub so to speak.

All the other projects have only one rule and that is to add every new task to Robotman. This way I only ever need to add or edit other rules in Robotman

Now when a new task is created because it waits till you navigate away from the task to run the robotman rule we are finding that task are not moving to the correct project because the teammember has already been assigned before the rule runs so it doesn’t trigger it again.

previously it was faultless, ronotman would run on creation and every action would have the desired effect

I hope that makes sense

Might be the reason right there. What’s your rule trigger? Assignee changed?

Yes exactly. in the past what happened was:

New task created

rule adds it to robotman

assigned to team member triggers robotman rule to add to specific project

easy peasy

Now, create new task

robotman rule does not run (until later)

Assign to team member, robotman rule does not run because it is not in robotman yet

I am sure that you can make it work again by playing with the triggers and conditions. Can we see a screenshot of the rule not running?

We are also running into this issue and now our tasks are in their wrong statuses since two rules are in waiting and will change the task custom fields once user has finished editing the task details. It was not like this before and this is annoying to have to do that one simple click. Isn’t automation supposed to help on these type of things? :smiley:

1 Like

I completely agree with the other feedback here; this seems like a step backwards. There are times when you would want the rule to run immediately; now it’s an extra step to have to click on the rule to run.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.