This article will describe how to check a workflow's error page and provide some helpful tips on how to interpret the information shown on the error page.
About workflow errors
Since the workflow acts as a "middle man", transferring data between separate apps and companies, there are several potential reasons for errors to occur. Common errors include:
- Connection issues (scheduled maintenance, internet dropouts, etc.)
- Validation errors (data from source app is not accepted in destination app, etc.)
- Missing data (required fields are missing, etc.)
In the event of an error you will receive an notification by email if you have enabled notifications.
You may then log into your account to view further details on the workflow error page.
How to find the workflow's error page
- Log into your account in CloudManager.
- The failed workflow will be marked with the text "Error - click to view".
Click the text to go to the workflow's error page.
Interpreting the error page
Please note: The workflow's error page may not contain sufficient information to resolve the underlying problem. If you have trouble interpreting the information on the error page, please contact email@example.com
The workflow's error page contains various technical information relating to the error, formatted as JSON.
It looks like this (sensitive information greyed out):
The fields indicate the following:
- Exception: This field will sometimes provide a clear description of the exact reason why the execution was stopped, and potentially how to resolve the problem.
However, if the exception message is a generic message (such as "TypeError"), please contact support for further information.
- Method: "GET" indicates that the workflow encountered the error while fetching data.
"POST" indicates that the workflow encountered an error while sending data.
- URL: The URL may indicate the type of data being fetched or sent.
- Response: The response shows the information returned from the destination app when attempting the data transfer. This will most likely contain the error message returned from the destination app API.
(In the above example, you can see that the destination app rejected the data transfer, saying "VAT code 5 is not valid for account 3200".)
- Payload: The payload shows what data the workflow attempted to transfer when it encountered the error. This may indicate which order number, customer, etc. caused the problem.
- Console: This section contains various information generated by the workflow in its run, that may or may not be helpful in determining the step at which the error occurred.
Please contact firstname.lastname@example.org if you have any questions or problems interpreting the error information.