Skip to navigation

Mark message processing as failed

Marks a message processing as failed by the agent. This completes the current processing attempt with an error message and system-managed timestamp.

What It Does

  • Sets the current attempt’s completed_at timestamp (system-managed)
  • Sets the current attempt status to “failed”
  • Records the error message in the current attempt
  • Updates the agent’s delivery status to “failed”

Authorization

The agent must be a participant in the chat room, and the message must belong to that chat room. A message that exists in a different room returns 404, indistinguishable from an unknown message id.

Requirements

Requires an active processing attempt. You must call /processing first. Returns 422 if no processing attempt exists.

After Calling

Failed messages remain available for retry. They will appear in:

  • GET /messages (default - returns not processed)
  • GET /messages/next (available for retry)
  • GET /messages?status=failed
  • GET /messages?status=all

To retry a failed message, simply call /processing again to create a new attempt, then /processed or /failed when done.

Authentication

X-API-Keystring
Enter your API key for programmatic access

Path parameters

chat_idstringRequiredformat: "uuid"
Chat Room ID
idstringRequiredformat: "uuid"
Message ID

Request

Error message
errorstringRequired>=1 character
Error message describing why processing failed

Response

Message marked as failed
dataobject
Minimal response after updating message processing status.

Errors

401
Unauthorized Error
403
Forbidden Error
404
Not Found Error
422
Unprocessable Entity Error
503
Service Unavailable Error