What is your goal?
Watch for asana subtasks completion and update the same record in airtable.
What is the problem & what have you tried?
I first built this scenario to watch for general asana task completions - and it worked only for parent asana tasks. I tried building another one and added a filter where âparent Idâ - exists. But I get this error message.
Error messages or input/output bundles
Error
Cannot initialize the scenario because of the reason âScenario validation failed - 1 problem(s) found.â
- Invalid reference in filter â0-0â on link before module â5â: Variable â1.parent.gidâ references not existing module â1â.
1 Like
The easiest way to solve this is to stop checking for the parent task too early.
The first Asana module only tells you that a task was completed. At that moment, Make does not yet know if it is a parent task or a subtask, so trying to filter on the parent field causes the scenario to fail.
Instead, you first let the scenario detect any completed task. Then, in the next step, you ask Asana for full task details. Only then do you check whether the task has a parent. If it does, you know it is a subtask and you can safely continue.
This way, Make never tries to read a field that does not exist.
First, use Watch Tasks in Asana and trigger the scenario when a task is marked as completed.
Next, use Get a Task in Asana and pass the task ID from the first module. This step always returns full information, including whether the task has a parent.
After that, add a filter that checks if the parent task ID exists. If it exists, the task is a subtask. If it does not, the task is a parent task and the scenario stops there.
Finally, once you know it is a subtask, use Update a Record in Airtable to update the correct record.
1 Like
I set it up exactly the way you said, whatâs happening is that itâs not even seeing my completed subtasks in the first module. I tested with completing a regular parent task, and the first 2 modules worked - and it was stopped at the filter. But then I completed a subtask and set it to run - it completed the operation with out picking up on anything. Which means that when I use the âwatch completed tasksâ module itâs not even seeing the subtasks.
1 Like
@Beth_Rochel
Did you resolve the error first? It seems not related to fetching the data from Asana but rather a filter that is placed before module 5 is referencing a non-existent variable that perhaps remained from the previous module before you swapped modules.
Additionally, I think it will be more beneficial to incorporate the usage of Asana webhooks in your Make scenarios and get notified on a Make scenario webhook when something completes in Asana.
Please evaluate these two insights, I hope they will help you.
EDIT: If the filter is adjusted yet the error persists - I had a similar issue when a scenario was stuck when trying to âRun Onceâ or âRun this module onlyâ - for some reason the scenario setup was stuck into the error and it only helped to redo it (either in the same or a new scenario). However, look into the above insights first.
Hey Beth,
the error shows you deleted a module but didnât delete a mapped item from said module inside a filter. So the filter is giving an error that the module its trying to pull data from doesnât exist.