Workflows error messages
An error that you encounter in a flow is dependent on the event, action, or function card that threw it. There are a number of scenarios in which an error may occur.
- Read the error message
- Array index out of bounds
- Cache error
- Invalid type conversion
- Method timeout exceeded
- API errors
You can read an error message in your flow in one of two ways:
Test a card: Click the Test this card icon on the card that's producing the error, then click the Test icon on the Test dialog.
This image is a sample error message for the Search for User action card in the Box connector.
Flow History: In the View History page for your flow, click the Error tab of the Flow History pane.
403 Forbidden HTTP error code in each example.
In some errors, you may encounter a more detailed message from the third-party connector where the error originally took place. In such cases, for example, an error may occur when an administrator doesn't have the proper privileges to execute a particular card in Workflows.
In addition to errors that are thrown in Workflows Designer, there are API messages that are produced as the outputs of action and event cards. For example, the following cards have HTTP status codes as their output, and will include an API error message if the card fails to execute a process:
This error occurs when a search by an action card fails. For example, this error may occur if you fail to find any users when executing the Read User action card in the Google Workspace Admin connector.
This error may also occur when processing a list in a flow and you specify an invalid index value. For example, this error will occur if you execute the At function using a value of 6 on a list of five items.
This flow execution error may occur when a flow is running while servers are restarting after a deployment. For example, a flow with a Read Table card may return an
Invalid or missing invariant lhs value error message if the card runs when deployments are taking place. Active flows that encounter this error must be restarted.
This error occurs when an action or function card expects a specific type of input but receives another that it can't convert. For example, if an integer input field in True/False Compare function card receives an unexpected object type, then the boolean process will not be executed and an error will be thrown.
This error occurs when an event, action, or function card attempts to perform an operation but fails to receive a response before exceeding a timeout value. Each card has an internal timeout setting which specifies the number of seconds after which it stops trying to perform an operation.