Working failed messages in Triage

Roles at a glance

Triage uses role-based access control. Your role determines which of the actions in this guide are available to you. Viewer, Operator, and Admin nest, each taking in the one before it; Developer sits to one side of that ladder — it authors transform scripts and does nothing else, so if it’s your role, most of this guide won’t apply to you.

Finding your way around

The main areas of Triage, and what each one is for.

Inspect a failed message

1. 1

   Open Queues and pick the DLQ you’re investigating — depth is shown next to each.

2. 2

   Triage peeks messages: they stay on the queue and are never consumed. On Anypoint MQ a peek takes a short peek-lock and the message returns automatically if you don’t act on it.

3. 3

   Click a message to open it. You get the full payload with syntax-highlighted JSON/XML, all attributes and headers, the receive count, and timestamps.

4. 4

   Use content filter and body-text search to narrow a large DLQ to just the messages you care about.

Edit and replay

1. 1

   Open a message and switch to the editor. The structured editor shows a live diff of your changes against the original body.

2. 2

   Choose a destination — the original source queue, or any other queue (including a queue on another provider when federation is configured).

3. 3

   Replay one message, or select many from the list and bulk-replay them in a single action.

4. 4

   Every replay is written to the audit log: who did it, what changed, the source and destination, and the before/after payload.

Write a JavaScript transform

1. 1

   Open Transforms and create a new script. A transform receives a message and can modify the payload and its attributes, reroute it to a different destination, or abort on a condition you define.

2. 2

   Test it in the browser before anything touches production traffic — the live panel shows the full output, including the attributes going out. An admin can load a real message from a queue to test against; a developer pastes in a sample instead, since real payloads are outside that role.

3. 3

   Save it. Every save that changes the name, description, or script writes a version, so you can review the history or clone an earlier one.

4. 4

   Then apply it when replaying: individually, across a bulk selection, or attached to an automated replay rule — that part is an operator or admin action.

5. 5

   Two guards protect live traffic. Once an enabled replay rule references a transform, a developer can no longer edit it in place — clone it, edit the copy, and have an admin promote it. And deleting a transform, which discards its version history too, is limited to the one you last authored unless you’re an admin.

6. 6

   Transforms are reusable — write the fix once and apply it everywhere the same failure shows up.

Automate with replay rules

1. 1

   Open Replay rules and create a rule. Match queues by glob pattern (*-dlq, orders-*) and filter messages by JSON path or body regex.

2. 2

   Attach an optional transform to adjust each message before it’s re-injected.

3. 3

   Set a cron schedule — e.g. every 15 minutes — and, with federation, route matched messages to a queue on another provider.

4. 4

   Always run a dry-run first: it shows exactly which messages would move, and where, without moving anything. Then enable the rule and let it drain the DLQ unattended.

Diagnose with AI

1. 1

   If your admin has enabled AI diagnosis, every message shows a Diagnose button.

2. 2

   Triage sends the payload, queue name, attributes, and sibling-message context to your configured LLM provider (Anthropic, OpenAI, or any compatible model) using your own API key.

3. 3

   You get back a structured result: probable cause, the affected fields, and suggested remediation steps.

4. 4

   No message data goes to any Triage-operated endpoint — the call runs from your network straight to your provider, billed to your account.

Remediate a poison object in storage

1. 1

   Open Storage. If more than one bucket is configured, pick one from the Bucket selector in the header — any bucket Triage currently can’t reach is flagged amber there, and the rest still work.

2. 2

   Find the object: walk the prefixes using the breadcrumb, or search by key. Deep buckets load a page at a time, so the count reads N+ shown until you’ve pressed Load more through to all loaded.

3. 3

   Click an object to open it. Above the body you get its size, last-modified time, content type, storage class, any custom metadata, and — in blue — the x-triage-* attributes carried over from the message that produced it. Those are what tie an object in a bucket back to the failure behind it.

4. 4

   To change it you need Operator or Admin; a Viewer sees the same object read-only. Edit the body in place and work across the pipeline tabs — Original → Edit → Transform → Diff — to apply a saved transform and read the exact diff before you commit. If the transform is erroring, Save and Replay both stay disabled, so nothing half-transformed can leave.

5. 5

   Save writes the corrected object back to the same key. Replay to queue sends it to a processing queue instead — or Replay to instance, when federation is configured, to a peer. Either way the object stays in the bucket; replaying doesn’t consume it.

6. 6

   Rename / move takes a new key and, with several buckets configured, a different destination bucket — including one on another provider. It copies server-side without loading the body, so it works on binary objects and on ones too large to open inline. If something already sits at the target key you get an explicit Overwrite confirm, and that one is permanent.

7. 7

   Delete is a soft delete: the object moves to the bucket’s trash prefix and can be restored from Storage Events until your bucket’s lifecycle rule reaps it. Storage Events is the log of every storage action, and it captures the original body — so you can also roll back a bad edit, not just an accidental delete.

Staying on top of it

Beyond fixing individual messages — how Triage keeps you informed, auditable, and oriented.