Acknowledging Failures¶

Failed Jobs, Work Orders, and Batches can be acknowledged to record that an operator has seen and triaged the failure. Acknowledgement is a lightweight, per-object flag stored in the object's Meta map. It does not change the object's state or stop any workflow; it only records that someone has looked at the failure.

This mirrors the behavior of Alerts and is used by the Operator Dashboard to keep already-triaged failures out of the "needs attention" metrics.

What gets recorded¶

Acknowledging an object writes three keys into its Meta:

Un-acknowledging is done by removing the acknowledged key from Meta.

Supported objects¶

Acknowledgement applies to:

• Jobs (jobs)
• Work Orders (work_orders)
• Batches (batches)

Acknowledging a Work Order from the Portal also acknowledges its current failed Job, so the pair clears together.

In the Portal¶

The Portal surfaces acknowledgement only for objects in the failed state. On the Jobs, Work Orders, and Batches tables you get:

• An Acknowledge button on a failed object's detail view.
• A clickable acknowledged column (a circle that fills in with a check) that acknowledges a row in place.
• A bulk Acknowledge action that acknowledges every selected failed row.
• A Show Failed button that filters the table to failed, not-yet-acknowledged rows.

The Operator Dashboard's failed-Job, failed-Work-Order, and failed-Batch metrics exclude acknowledged objects, so acknowledging a failure removes it from those counts.

Filtering¶

To list only unacknowledged failures, combine a state filter with an acknowledged filter:

State=Eq(failed)&Meta.acknowledged=Ne(true)

Meta.acknowledged=Ne(true) matches objects that have not been acknowledged (the key is absent or not "true").

Acknowledging outside the Portal¶

Because acknowledgement is just object Meta, it can also be set through the API or the CLI.

API¶

PATCH the object with a JSON-Patch that adds the Meta keys, against PATCH /api/v3/jobs/{uuid} (or work_orders, batches):

[
  { "op": "add", "path": "/Meta/acknowledged", "value": "true" },
  {
    "op": "add",
    "path": "/Meta/acknowledge_time",
    "value": "2026-07-21T15:04:05Z"
  },
  { "op": "add", "path": "/Meta/acknowledge_user", "value": "operator1" }
]

CLI¶

drpcli can set the same Meta with an update (a merge patch):

drpcli jobs update <uuid> '{"Meta": {"acknowledged": "true"}}'

Replace jobs with work_orders or batches as needed.