Issues with workflow

Status: Open · Asked by Dan Cook on · 0 views

Dan Cook — Question ·

This workflow does not seem to be completeing properly.
It gets to the API module and then just stops. It doesn't trigger the second iteration and all subsequent steps.
Can you please advise?

Preeti Paryani — Reply ·

Hey @dan90,

Thanks for reporting this.

We’ll need some time to reproduce the behavior on our end and will also escalate it to our technical team for further investigation.

As soon as we have an update, we’ll get back to you.

Appreciate your patience.

Preeti Paryani — Reply ·

Hey @dan90,

Thanks for your patience.

We’ve been able to narrow this down and it appears that the issue is occurring specifically when there is a Delay step placed before the next iteration. In such cases, the second iterator and subsequent steps are not getting displayed, but they are executed.

For now, we recommend removing the Delay step from that position in your workflow. This should allow the workflow to execute completely, including the next iteration.

Our team is already looking into this behavior. Once it is fully resolved, you should be able to add the Delay step back without issues.

Please try this and let us know how it goes.

Dan Cook — Reply ·

Thank you Preeti
I'll let you know how I get on.

Dan Cook — Reply ·

One thing to note, my next steps after the 2nd iterator involve an "add row" to a google sheet. This did not occur for any iteration unfortunately. So it appears to have stalled at the point that is shown in the history.

Preeti Paryani — Reply ·

Hi @dan90,

Thank you for getting back to us and for highlighting this point.

There could be a reason why the Google Sheets “Add Row” action did not execute in your case. However, when we tested this on our end, the steps after the second iterator worked correctly and data was successfully added to the application.

At the moment, since the task history is not fully visible, we’re unable to pinpoint the exact cause from your execution. It’s possible that an error occurred during runtime which isn’t currently being displayed.

Our team is actively working on this issue. Once it is resolved and the task history executes and displays properly, we’ll be in a better position to confirm whether the Google Sheets step is working or identify why it might be failing.

In the meantime, you may either follow the workaround shared earlier (removing the Delay step) or wait until the fix is implemented.

We appreciate your patience.

Preeti Paryani — Reply ·

Hey @dan90,

The reported issue has now been resolved. It should work fine going forward.

Back to all forum threads · Log in to reply