Succes returns a failure - how can I countdown the Iterator steps?

[apps]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjEwNTY5MDYzNjA0M2M1MjZlNTUzMyI_3D_pc

Your Task History ID

IjU3NjUwNTZhMDYzNjA0MzQ1MjZjNTUzNzUxMzY1MTYyNTQzNzBmMzQi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

See this video please:

Zight Recording 2025-10-15 at 10.46.16 AM

Shared with Zight

share.zight.com

It shows the issue as it is hard to explain without visuals.

 

[apps]

Have a similar issue here. If already have a filter that says that it should only continue if this return 204 so how can i avoid it listing itself as a failure:
- Timing: Delete timeentry : Execute API Request fails

Flow: https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY1MDYzMTA0MzQ1MjZjNTUzNTUxMzci_pc

Task history: IjU3NjUwNTZhMDYzNjA0MzQ1MjZjNTUzNzUxMzY1MTY1NTQzNDBmMzEi_pc

How can i solve this?

Also if you had a simple checkbox for each Pabbly Actions saying "Don't trigger errors on failure", this would be instantly solved. Then in this case where I'm trying to delete a project that doesn't exist, it wouldn't return an email with an error. This would completely work around all these types of errors.

 

[Preeti Paryani]

Hello @apps,

Please allow us some time to review both of your concerns. We will escalate them if required or provide you with a suitable workaround. We’ll get back to you with an update as soon as possible.

 

[Preeti Paryani]

Hello @apps,

Thank you for sharing the screen recording and workflow details.

Upon reviewing both, we weren’t able to fully interpret your complete infrastructure setup. However, based on the video, it appears that the error occurs only under a specific condition — for example, when a certain item or entry being deleted no longer exists.

In such cases, we’d suggest adding a router after the deletion step. You can first check whether the item still exists — if it does, proceed with the deletion; if not, route the workflow to skip that action. This will prevent the step from returning an unnecessary failure.

Regarding the Iterator, at the moment it isn’t possible to directly count how many times it has been executed. While you could technically set up a counter using a number formatter or variable update, this may not be consistent if the array length varies dynamically.

For now, adding conditional routing as suggested should help prevent the unwanted error triggers.