Checkpoint
Use this node to hand off processing to a different queue — for example, to move a message from a high-throughput queue to a lower-priority one, or to isolate computationally expensive processing into a dedicated queue with its own rate limits and retry policy. Once the copy of the message is successfully enqueued, the original message is acknowledged.
Configuration
Section titled “Configuration”| Field | Required | Description |
|---|---|---|
| Queue name | Yes | The name of the target queue to transfer the message to. |
Message processing algorithm
Section titled “Message processing algorithm”- The node receives an incoming message.
- A copy of the incoming message is created and enqueued to the configured target queue.
- Once the copy is successfully enqueued, the original incoming message is acknowledged.
- If enqueueing fails, the original message is routed via the
Failureconnection without being acknowledged.
Output connections
Section titled “Output connections”| Connection | Condition |
|---|---|
Success | The message copy was successfully enqueued and the original was acknowledged. |
Failure | An error occurred while enqueueing the message. |
JSON schema
Section titled “JSON schema”{ "$schema": "https://json-schema.org/draft/2020-12/schema", "title": "TbCheckpointNodeConfiguration", "type": "object", "required": ["queueName"], "properties": { "queueName": { "type": "string", "description": "Name of the target queue to transfer the message to." } }, "additionalProperties": false}