Flow steps after “Proceed to Next Application” Doesn’t Run After Retry?

Integrator.io
,
1

Hi everyone,

I have a flow in Celigo where one step has Error Handling with Proceed to the next application regardless enabled.

image
image435×229 9.2 KB

The image displays a dialog box asking what should happen to a record if a lookup fails, with options to proceed regardless or pause until the error is fixed. (Captioned by AI)
The image displays a dialog box asking what should happen to a record if a lookup fails, with options to proceed regardless or pause until the error is fixed. (Captioned by AI)455×245 13.9 KB

When that step fails, the flow continues and updates records in NetSuite with a "failed" status on specific lines, which is what I want.

But when I retry that failed step, it seems the flow doesn't continue to the next steps anymore.

Is this normal behavior when retrying?

2

Yes, this behavior is expected because the record would have been processed in the initial flow run, despite encountering errors in the lookup step.

3

Ah, that makes sense.
It would be helpful to have a setting that lets retries execute all following steps too, giving users the choice based on their needs.

4

@nuriensing .... what's the use case you have in mind there?

5

Hi,

We are currently sending Order Confirmations (OCs) to SAP Ariba.

Without going too much into the details: in NetSuite, we have opportunities with line items. Each line item can trigger an OC, depending on several variables. This logic is complex and involves multiple decision points.

Typically, when we post an OC to Ariba, we receive either a success or error response:

  • If the response indicates an error, we update the related records in NetSuite with the status "OC rejected by Ariba", along with the corresponding error message.
  • If the response is successful, we update the records with "OC submitted."

These statuses are critical for downstream processing in both NetSuite and Celigo.

When we receive an error, we review the message before taking further action. For example, earlier today we received an "unknown error" from Ariba. After retrying the same request, it was processed successfully, but the associated NetSuite records were not updated to reflect this.

This results in inaccurate status tracking for OCs that are ultimately accepted by Ariba, which can lead to issues in subsequent processing.