Actions8
Overview
This node integrates with AWS Step Functions, specifically enabling you to report a task failure back to a Step Functions workflow. When a task assigned by Step Functions fails during execution, this node sends the failure information including an error code and a detailed cause message using a task token that uniquely identifies the task.
Common scenarios include:
- Handling asynchronous or long-running tasks where your workflow needs to be notified if a task cannot complete successfully.
- Reporting errors from external systems or services back to AWS Step Functions to trigger compensating actions or retries.
- Integrating custom workers or microservices with Step Functions workflows to provide real-time failure feedback.
Example: If a workflow delegates a job to an external service and that service encounters an error, this node can send the failure details back to Step Functions so the workflow can handle it accordingly (e.g., move to a catch state).
Properties
| Name | Meaning |
|---|---|
| Task Token | The unique token representing the specific task assigned by Step Functions. This token is required to identify which task failed. |
| Error | The error code string describing the type of failure encountered. |
| Cause | A more detailed explanation or message describing the cause of the failure. |
Output
The node outputs a JSON object reflecting the response from the AWS Step Functions API after sending the task failure. Typically, this response is empty or contains metadata confirming the failure was reported successfully.
No binary data output is produced by this operation.
Dependencies
- Requires valid AWS credentials with permissions to interact with AWS Step Functions.
- The node uses the AWS SDK internally, so no additional external dependencies are needed beyond proper credential configuration.
- You must configure AWS access key ID, secret access key, and region in the node's credentials settings.
Troubleshooting
- Invalid or expired task token: If the task token is incorrect or expired, the API call will fail. Ensure the token is copied correctly from the Step Functions context.
- Insufficient permissions: Make sure the AWS credentials used have permission to call
SendTaskFailureon the relevant Step Functions resources. - Malformed error or cause strings: Passing invalid JSON or overly large strings may cause errors. Keep error and cause concise and properly formatted.
- Network or AWS service issues: Temporary connectivity problems or AWS service outages can cause failures; retrying later might help.
Common error messages:
- "Task does not exist or is not running" — indicates the task token is invalid or the task has already completed.
- "AccessDeniedException" — indicates missing permissions for the AWS credentials.
Resolving these usually involves verifying tokens, permissions, and network connectivity.