Unexpected Large Number of Tasks Used

[adampj]

Your Task History ID

IjU3NjUwNTZlMDYzNDA0MzU1MjZjNTUzZDUxM2I1MTYzNTQzMjBmMzQi_pc

Hi Pabbly Team,

I'm looking for some advice please on: https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY5MDYzNDA0M2Q1MjZkNTUzMTUxMzYi_pc

I expected it to use a total of 4 tasks per run - 1) Todoist Import 2) GCal Import 3) ChatGPT Output 4) Todoist Task Creation, however instead of 4 tasks, it's using 141 tasks

I wonder if anyone might be able to help advise me please as to what I've done wrong here, and what the large number of tasks were used for? After looking at the history and logs to see where this number is being used from, I'm still struggling to understand. I have disabled this rule for the moment.

Thanks for your assistance/time,

Adam

 

[adampj]

Note: I've just seen a large number of final tasks created at Step 4# - it seems like somehow the task looped around. I'm not sure where I've gone wrong, I may have to just start again with a fresh new rule and re-build. Any advice or info you can share would be appreciated all the same. I'll leave disabled until I can figure out why it created so many tasks. Thank you.

 

[adampj]

This looks to be correct:

However "Todosit: Create a Task" is the last step of the workflow. However, looking at the logs, it seemed to repeat Data Transformer again and again...

Perhaps relating to the order of my steps - it look like "Process Arrays" might something to do with this. Maybe I need to revisit the work flow order.

 

[Himesh]

This looks to be correct:

View attachment 54005

However "Todosit: Create a Task" is the last step of the workflow. However, looking at the logs, it seemed to repeat Data Transformer again and again...

View attachment 54008

Perhaps relating to the order of my steps - it look like "Process Arrays" might something to do with this. Maybe I need to revisit the work flow order.

Can you please check task history of this workflow? By checking that you might get idea why it has used these much of tasks.

FYI I'm not from pabbly team. I'm an automation freelancer who helps other pabbly members. And if still confused or have some doubts you can dm me. We can do free zoom call.

 

[adampj]

Thanks @Himesh, appreciate the message/support!

I think I've now identified the issue - this is a useful quote I've found from @Preeti Paryani RE using Iterator:

Please note that when you click the Save and Send Test Request button, only the first object of the array will be displayed in the response. However, during runtime, all steps added after the Iterator will execute for each object in the array, based on the number of objects it contains.

Source: Iterator Post

Where I think I've gone wrong here was that by using the iterator, it was then re-processing all actions post-iterator step for every object in the array.

I'm now re-building and will try a slightly different variation! Thanks for the message all the same @Himesh

 

[adampj]

The iterator was the issue here. As I was trying to filter the return outputs within Pabbly, it actually made sense to filter on the API calls themselves. I reworked a new process using Data Transformer and now all is working correctly under 4 tasks. Thanks!

 

[ArshilAhmad]

Thank you for the update. We are glad the issue is fixed now.