Process flow run failures
Last updated
Last updated
A process flow may fail for a number of reasons - for example, if a mapped field in the source/destination system has changed unexpectedly; if authentication credentials for a connection have expired, or if shape configuration is incorrect.
You might notice the failure whilst observing real-time logs as a flow is run manually, or you might have received an email alert advising that an auto-triggered process flow failed to complete.
This guide summarises what to do in the event that a process flow fails.
Step 1 Check the run logs for the process flow. Here you'll find detailed information associated with each step in the flow, so you can identify which shape caused the flow to fail.
If you change credentials for an instance, those credentials will be updated in all process flows where that instance is defined.
Step 2 If the cause of the failure isn't obvious from the log details, check the payloads for each step in the flow to see if they are as expected. Payloads are available from the run logs page, via the view logs option for each step:
Step 3 If you've found the cause of the failure from the logs and need to update the process flow, access the process flow in question and make the required changes. OR If you haven't found the issue and need to investigate further, access the process flow in question and check the settings for each shape.
Step 4 Having updated the process flow, you may wish to run it manually to check that the issue is resolved or wait for the next scheduled run.