Error sending email after branching path -- Can't find Asaan Task ID

Hi @kchristensen 

NOTE: If you want the path filters to check for current Asana Task data after the Delay, then you need to add a step to find the same Asana Task again, then map those values into the Path filter conditions.

Check your Zap Runs history details to see the DATA IN/OUT for each step to help you troubleshoot.

Zap Runs: https://zapier.com/app/history/

Can you post screenshots showing the encountered error from your Zap Runs?

Strange. I’m pretty sure in my troubleshooting I’ve successfully had this Zap move the item from one section to the next after a delay without adding that step. 

@kchristensen 

You don’t need to add that step, but the Task data may have changed during the delay time.

So if you don’t fetch the same Asana Task again after the delay, the Filter conditions are using “outdated” data, which depending on your logic, may cause the Zap Run to not process as expected.

Can you tell me the name of the step I need to add? How would I fetch the Asana task without using the Asana Task gid from the trigger step?

That worked! Thank you for your help.

That’s awesome! We’re glad to hear that the issue is now resolved!

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 🤗