Actions26
Overview
The "Retry" operation under the "Messages" resource allows users to retry sending a previously failed message job. This is useful in scenarios where message delivery has failed due to transient issues such as network problems, platform outages, or temporary API errors. By retrying the failed message job, users can attempt to resend the message without manually recreating it.
Practical examples include:
- Automatically retrying failed notifications sent via messaging platforms like Telegram, Discord, or WhatsApp.
- Recovering from temporary failures in message delivery pipelines.
- Ensuring critical messages are eventually delivered by retrying failed jobs programmatically.
Properties
| Name | Meaning |
|---|---|
| Failed message job ID (jobId) | The unique identifier of the failed message job that you want to retry. |
| Project Slug | The identifier (slug) of the project under which the message job exists. |
Note: There are duplicate property definitions for jobId with slightly different descriptions but they refer to the same required string input representing the job ID.
Output
The node outputs the JSON response returned by the API after attempting to retry the failed message job. This typically includes details about the retry request status and any relevant metadata about the retried message job.
There is no indication that this operation outputs binary data.
Dependencies
- Requires an API key credential for authentication to the GateKit messaging gateway API.
- The node makes HTTP POST requests to the endpoint
/api/v1/projects/{projectSlug}/messages/retry/{jobId}. - The user must provide a valid project slug and the job ID of the failed message to retry.
Troubleshooting
- Invalid or missing job ID: If the job ID is incorrect or not provided, the API will likely return an error indicating the job cannot be found. Ensure the correct job ID of the failed message is used.
- Invalid project slug: Using an incorrect project slug may cause the API to fail to locate the project or message job.
- Authentication errors: Missing or invalid API credentials will result in authorization errors.
- API rate limits or service downtime: Temporary API unavailability or rate limiting could cause retries to fail; consider implementing retry logic with backoff.
- Message permanently failed: Some messages might not be retryable if they have permanent failure states; check API response for such indications.
Links and References
- GateKit API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on creating custom nodes and using HTTP Request nodes for API integration