Reprocess Message

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

const response = await fetch('http://localhost:9090/reprocess_message', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    origin_id: 1399811149,
    message_id: "0x9484bd5c635b17b28cb382249d7a6fe5ca15debfd4f824247c68d47badc5b7de"
  })
});

import requests

response = requests.post('http://localhost:9090/reprocess_message', json={
  'origin_id': 1399811149,
  'message_id': '0x9484bd5c635b17b28cb382249d7a6fe5ca15debfd4f824247c68d47badc5b7de'
})

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

{
  "error": "Invalid message_id format"
}

{
  "error": "Message or context not found"
}

POST

reprocess_message

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

const response = await fetch('http://localhost:9090/reprocess_message', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    origin_id: 1399811149,
    message_id: "0x9484bd5c635b17b28cb382249d7a6fe5ca15debfd4f824247c68d47badc5b7de"
  })
});

import requests

response = requests.post('http://localhost:9090/reprocess_message', json={
  'origin_id': 1399811149,
  'message_id': '0x9484bd5c635b17b28cb382249d7a6fe5ca15debfd4f824247c68d47badc5b7de'
})

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

{
  "error": "Invalid message_id format"
}

{
  "error": "Message or context not found"
}

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.

Show Request Body

u32

required

Domain/chain ID where the message originated

string

required

Hex-encoded message identifier (H256)

Show Response Body

boolean

Whether the message was successfully re-queued for processing

string

Details about the reprocessing operation

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

const response = await fetch('http://localhost:9090/reprocess_message', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    origin_id: 1399811149,
    message_id: "0x9484bd5c635b17b28cb382249d7a6fe5ca15debfd4f824247c68d47badc5b7de"
  })
});

import requests

response = requests.post('http://localhost:9090/reprocess_message', json={
  'origin_id': 1399811149,
  'message_id': '0x9484bd5c635b17b28cb382249d7a6fe5ca15debfd4f824247c68d47badc5b7de'
})

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

{
  "error": "Invalid message_id format"
}

{
  "error": "Message or context not found"
}

Introduction

Key Management

Validators

Relayer

Agent Config

Guides