Bananajuice2002
Member
- Your Task History ID
- IjU3NjIwNTZhMDYzNzA0Mzc1MjZmNTUzNDUxMzc1MTYxNTQzOSI_3D_pc
I'm facing an issue with the Iterator and Airtable action, as they do not update rows that are in sequence.
1.Schedule Time
2.Get all records from Airtable (Simple Response)
3.Iterator
4.Filter (from Iterator) = Success
5.Creatomate (Get Template)
6.Text Formatter
7.Text Formatter
8.Text Formatter
9.Creatomate Render (Modifications)
10.Delay (3 min)
11. Airtable (Update row from Iterator by record ID)*
12. Error Filter is not set ( that is with record 4th)*
The problem arises in the 11th step. Although it shows as successful, the attachment does not appear in the Airtable row. This is perplexing, especially considering that the first two rows were updated successfully. Furthermore, the 4th row record in Pabbly cannot be initiated because the task history states: 'The filter is not set,' even though the filter used was the same as in the 1st, 2nd, and 3rd rows.
Please let me know what I should change or add. I am considering adding an additional Airtable action: Search, and then mapping the final step (11th) with the response from the Search step.
1.Schedule Time
2.Get all records from Airtable (Simple Response)
3.Iterator
4.Filter (from Iterator) = Success
5.Creatomate (Get Template)
6.Text Formatter
7.Text Formatter
8.Text Formatter
9.Creatomate Render (Modifications)
10.Delay (3 min)
11. Airtable (Update row from Iterator by record ID)*
12. Error Filter is not set ( that is with record 4th)*
The problem arises in the 11th step. Although it shows as successful, the attachment does not appear in the Airtable row. This is perplexing, especially considering that the first two rows were updated successfully. Furthermore, the 4th row record in Pabbly cannot be initiated because the task history states: 'The filter is not set,' even though the filter used was the same as in the 1st, 2nd, and 3rd rows.
Please let me know what I should change or add. I am considering adding an additional Airtable action: Search, and then mapping the final step (11th) with the response from the Search step.
