Skip to main content
POST
/
reprocess_message
curl -X POST "http://localhost:9090/reprocess_message" \
  -H "Content-Type: application/json" \
  -d \
'{
  "origin_id": 1399811149,
  "message_id": "0x9484bd5c635b17b28cb382249d7a6fe5ca15debfd4f824247c68d47badc5b7de"
}'

{
  "success": true,
  "message": "Message re-queued for processing"
}

Documentation Index

Fetch the complete documentation index at: https://docs.hyperlane.xyz/llms.txt

Use this file to discover all available pages before exploring further.

Re-queue a message for processing on demand. This endpoint allows external services to trigger message delivery instead of relying on queue backoff, and can handle scenarios like blockchain network reorganizations or manual message processing.
For purely on-demand processing without automatic retries, combine this endpoint with max_message_retries := 0 in your relayer configuration. This ensures messages are only processed when explicitly triggered via this API.
curl -X POST "http://localhost:9090/reprocess_message" \
  -H "Content-Type: application/json" \
  -d \
'{
  "origin_id": 1399811149,
  "message_id": "0x9484bd5c635b17b28cb382249d7a6fe5ca15debfd4f824247c68d47badc5b7de"
}'

{
  "success": true,
  "message": "Message re-queued for processing"
}