Asana to ClickUp Zaps: Duplicate tasks & API Errors

Hi @tatazildo 

For the duplicates, check your Zap Runs history details to see the DATA IN/OUT for each step to help you trace and troubleshoot: https://zapier.com/app/history/

You may need to add a Delay (After Queue) step to the Zap to help prevent duplicates as that will achieve sequential processing of Zap Runs: https://zapier.com/apps/delay/help

Hi @Troy Tessalone and thanks for the help.

I have added a Delay After Queue step to Zap 2, created a new Test Task and waited for it to process. I got 2 tasks in ClickUp (one being a duplicate) and three Zap runs:

1. Expected Zap 1 run: new task was created in specific project in Asana and then new task was sent to ClickUp matching the task in Asana. This run generated ClickUp task ID 86a42gazk. Perfect.
2. Zap 2 ran as soon as Zap 1 ran, at the same time each, two times, each time with a 2 task usage (I’m not sure why):
   1. First run chose path “Task doesn’t exist in ClickUp”, which expects a ”false” bolean result based on a search step (see attachment below of updated Zap 2 with steps expanded). This is also incorrect, as the task did exist in ClickUp since it was created by Zap 1. This means it generated a new task in ClickUp with ID 86a42gcyf (the duplicate).
   2. Second run chose path “Task exists in ClickUp”, which is correct, but found task ID 86a42gcyf (the duplicate from the first Zap 2 run) and not ID 86a42gcyf from Zap 1 run.

Zap 2 shouldn’t have run in first place, since the task was only created, but never updated/modified since creation. Even if it should’ve ran, it should’ve found ClickUp task ID 86a42gazk, resulting in “true” for the search step and thus not ran at all.

Also, I noticed that the trigger of each of the Zap 2 runs is a change in the “section” field, which I guess is automatic:

Can I filter my Zap to not track these kinds of changes anymore? They seem to happen as soon as a new task is created.

@tatazildo 

Try removing the Delay from Zap 1.

Troy Tessalone wrote:

@tatazildo

Try removing the Delay from Zap 1.

 

@Troy Tessalone thanks but I already did. I figured this delay was unnecessary as I was reviewing my Zaps after posting.

@tatazildo 

When an Asana Task is created there can be sub processes in Asana that run to update the Asana Task, thus causing the Asana Task to be considered “updated”.

If a new Asana Task is also triggering the updated Asana Task, then you can not need Zap 1.

@Troy Tessalone you’re right. I’ve disabled Zap 1 and also adding a Delay like you suggested is apparently working well for controlling multiple changes to an Asana Task by queuing every individual change.

Now the only part that’s bothering me is that two subprocesses run each time a task is created, the adding of two (not one like I posted, I’ve double-checked it) sections with different GIDs to a newly created task. This results in two Zap 2 runs every time, each one using 2 Zapier tasks off my limit.

@tatazildo 

Sounds like you’ll need to add a condition to a Filter step to filter for only the desired data field value to limit it to only 1 Zap Run.

@Troy Tessalone yes. I’ve tried this but I can’t target this “section” field using the Zap Editor UI. Also, just to leave it here: Asana apparently works with “due_at” and “due_on”, and also both are updated when the Asana task’s due date field is changed, also resulting in one separate Zap run for each event. This event I was able to filter by using “Change Field” to “due_at” using ““Does not match”.

@tatazildo 

Check the Zap Runs history details to see the DATA IN/OUT for each step to help you determine which data points can be used in the filter to isolate the desired changes: https://zapier.com/app/history/
 

NOTE: The same issues may happen for future updates on an existing Asana Task.

@Troy Tessalone I did. Like I said, I can filter “due_on”/”due_at” because they’re a change “field”, so you can target them using the “Change Field” field using the Zap edit UI:

@tatazildo

For an Asana Task change it appears the “action” is always present. (e.g. added, changed)

But the change “key” label (e.g. field vs section vs etc) appears to vary depending on the “action”.

You’ll have to use a different Zap step example to get a change that is related to a section in order to use that data point in the left side of a filter condition.

Help article about changing Zap trigger test examples: https://help.zapier.com/hc/en-us/articles/8496310366093-Change-the-test-record-in-your-Zap-trigger

Troy Tessalone wrote:

@tatazildo

For an Asana Task change it appears the “action” is always present. (e.g. added, changed)

But the change “key” label (e.g. field vs section vs etc) appears to vary depending on the “action”.

You’ll have to use a different Zap step example to get a change that is related to a section in order to use that data point in the left side of a filter condition.

Help article about changing Zap trigger test examples: https://help.zapier.com/hc/en-us/articles/8496310366093-Change-the-test-record-in-your-Zap-trigger

 

 

@Troy Tessalone all your affirmations are correct, but I think Zapier only offers the alternative to target the label “field”, and not any other such as “section”.

@tatazildo 

For live Zap Runs, the data returned from Asana changes based on the “update” made to the Asana Task.

Seems like the returned Zap trigger examples only show examples with field changes.

It will likely involve a bit of a workaround.

You can use a Zap step: Formatter > Text > Default Value

This will always return a variable that you can then map into the Filter step condition.

In the Formatter step, you can use named variables to set a variable for “section”.

{{XXX__change__section}}

• Create your own fields with Named Variables