Common Workflows errors
At runtime, Workflows can emit a number of error types to point out problems when you're executing your Flows. This table describes Workflows error codes.
|A TCP connection couldn't be initialized to an external service.
|An error occurred in the file system.
|Access to a resource is forbidden.
|An external service returned an HTTP error. The message may contain a 500 status code and no content in the response body.
|HTTP Request Error
|An external service returned an HTTP error, but it contained information in the response body that described the underlying error.
|The flow was invalid and couldn't be parsed or executed.
|An input is missing or invalid on a system module.
|Invalid Type Conversion
|A type conversion operation couldn't be completed
|A low-level networking error occurred during an attempt to communicate with another internal or external service.
|A Flow isn't active and can't be executed.
|A resource wasn't found.
|OAuth Refresh Error
|An OAuth refresh failed.
|A value couldn't be parsed, such as JSON or XML.
An individual step in a Flow took more than 10 minutes to run. This type of error often points to an infrastructure issue.
|A URL is invalid.
|An unspecified error.
|An unspecified user error.