7.2.3 How to deal with workflow errors
You can check the execution status of a workflow in the [Execution Log] window for the workflow. For details about the [Execution Log] window, see “Workflow [Execution Log] window”.
If an error appears in the [output] section of [Action Output] in the workflow’s [Execution Log] window, the resolution varies depending on the nature of the error. This section explains common error examples and their resolutions.
(1) When stderr appears in the first level
[Example]
{
"stderr": "command not found: invalid_cmd¥n",
"stdout": "",
"return_code": 127
}
"stderr": "command not found: invalid_cmd¥n",
"stdout": "",
"return_code": 127
}
[Main causes]
- Command or script failure
- Timeout
- Permission issues
- SSH connection issues
[Resolution]
- Check the contents of “stderr” and the value of “return_code” to identify specific error messages or warnings.
- Verify the execution environment of the command or script (paths, permissions, and dependent files).
- If the cause is a timeout, review the execution time and check resource availability.
- If the cause is an SSH connection issue, verify authentication credentials and network settings.
- Check the script logic and command arguments.
(2) When “error” or “errors” appears at the first level
[Example]
{
"error": "Action 'invalid.action' not found",
"errors": ["Parameter 'host' is required but not provided"]
}
"error": "Action 'invalid.action' not found",
"errors": ["Parameter 'host' is required but not provided"]
}
[Main causes]
- Actions or runners return errors, such as syntax errors in the Workflow YAML file or inconsistencies in task definitions.
[Resolution]
- Check the error message and error code to identify the cause of the error.
- Refer to the action’s specifications and documentation to verify the error conditions.
- Check the action’s parameters and preferences.
(3) When “error” or “errors” is displayed nested within “result”
[Example]
{
"result": {
"error": "HTTP 404: Resource not found",
"status_code": 404,
"data": null
}
}
"result": {
"error": "HTTP 404: Resource not found",
"status_code": 404,
"data": null
}
}
[Main causes]
- The action returns both data and an error simultaneously.
[Resolution]
- Carefully review the error information within “result” to identify the process where the issue occurred.
- Investigate the cause by referring to the HTTP response status code and error message.
- Verify the correct endpoint and parameters in the API specification document.
- Verify the authentication token.