Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The "Messages: Retry" operation in this node allows users to retry sending a previously failed message job within a specified project. This is useful in scenarios where message delivery has failed due to transient errors or network issues, and you want to attempt resending the message without creating a new message from scratch.
Practical examples include:
- Automatically retrying failed notifications sent via messaging platforms.
- Manually triggering a retry for a specific failed message job identified by its job ID.
- Integrating with monitoring workflows that detect failed messages and trigger retries.
Properties
| Name | Meaning |
|---|---|
| Failed message job ID | The unique identifier of the failed message job that you want to retry. |
| Project | The identifier of the project under which the message job exists. |
| JobId | Alias for the failed message job ID parameter (same as "Failed message job ID"). |
Note: The properties "Failed message job ID" and "JobId" represent the same value and are required to specify which failed message job to retry.
Output
The output of this operation will be JSON data representing the result of the retry request. Typically, this includes confirmation that the retry was accepted or details about the retried job status.
The node does not explicitly mention binary data output for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the messaging gateway API.
- The node sends HTTP POST requests to the endpoint
/api/v1/projects/{project}/messages/retry/{jobId}. - The user must have access rights to the specified project and message job.
Troubleshooting
- Common issue: Providing an incorrect or non-existent job ID will likely result in an error indicating the job was not found.
- Resolution: Verify the job ID corresponds to a failed message job in the specified project.
- Authentication errors: If the API key credential is missing or invalid, authentication failures will occur.
- Resolution: Ensure the API key credential is correctly set up and has permissions for the project.
- Project not found or unauthorized: Errors may occur if the project identifier is wrong or the user lacks access.
- Resolution: Confirm the project ID is correct and accessible with your credentials.
Links and References
- No direct external links provided in the source code.
- For more information on message jobs and retry semantics, consult the messaging gateway API documentation relevant to your platform.