Understanding how Asana triggers chain

I am trying to understand how Asana manages triggers with a little more granularity. Here is what we have set up.

  1. Asana form submits to a routing project.
  2. Routing project contains two triggers:
    • [A] On form-task-type field change, move this Task to a regional-operational project.
    • [B] On form-location field change, update a province-location field based upon the form-location.
  3. The regional-operational project contains another trigger:
    • [C] On province-location field change, add this Task to an province-operational project.

What we have noticed is that sometimes the trigger [C] does not fire. My best guess at this point is that in some cases trigger [B] executes BEFORE [A] and therefore when the Task hits the regional-operational project, there is no province-location change to trigger [C]. The province-location change has already happened. Is that a reasonable conclusion? Any potential insight would be helpful!

Hi @Randy_Ostridge , from my experience with having rules multi-home a task to another project, I found that adding ‘Task added to project’ as part of the triggers usually helps.

In your regional-operational project, add this trigger along with your province-location field change trigger (use the + sign) to your rule C. I dont think the order matters. Just make sure that at the top of your triggers, select ‘when ALL these happen’. (not ANY)

I find that this solution allows the project that the rule is being multi-homed to react correctly (your regional-operational project, in your case)

Try it and let me know if this helps :wink:

What I can tell you is that you can’t have control over when rules run and their order.

I am not sure if it applies to your case, but we sometimes had to rely on “pivot fields”: extra fields used to store the info of previous states.