Skip to content

Learn · Guides

Handle a review

Decide a call the platform held for a person.

Checked against the product on · written for people who run the account

When a rule proposes a sensitive action, the platform stops and puts the call in the review queue. Nothing happens to your systems until a person decides.

console.dmzagent.com/reviews

Watch

Reviews

1WaitingMineHandled
2
Watched thingWhat firedWants toWaitingAction
pump-12temperature-excursionTurn off access4 minutesClaim
acct-4471credential-exposureOpen a ticket11 minutesClaim
bot-supportoff-topic-answerBlock26 minutesClaim
Figure. The review queue. Each row is one held action waiting on a person. The review queue with three calls waiting for a person, each with what fired, what it wants to do, and Claim.

  1. Open Reviews.1

    Waiting holds every unclaimed call. Mine holds the ones you claimed.

  2. Select Claim on the row you are taking.2

    Claiming stops two people working the same call.

Read the call

console.dmzagent.com/reviews

Watch

Review · pump-12

1Held for a person. Nothing has happened yet.
2
Wants to
Turn off access for pump-12
Why
temperature-excursion crossed the build-up threshold
Rule
Overheat hold
Evidence
6 events, 12:03:44 to 12:04:11
3DeclineChange the actionApprove
Figure. One review: the held action, the reason, and the evidence behind it. One review, showing the held action, the reason, the evidence, and Approve, Change and Decline buttons.

  1. Read the banner.1

    It confirms the action is still held.

  2. Read the reason and the evidence.2

    The evidence names the events that led here and the window they arrived in. Selecting it opens the events.

  3. Select Approve, Change the action, or Decline.3

    Approve dispatches the action. Change swaps it for another from the fixed list. Decline closes the call and leaves your systems untouched.

Safe by default. Every one of the three outcomes is written to the logbook with your name, the time, and the reason you gave. A declined call is as much a record as an approved one.

Closing the loop

An approved fix leaves the platform and lands in your systems. Tell the platform when it completed, and the decision record closes.

curl -X POST 'https://api.dmzagent.com/v1/agent-outputs/OUTPUT_ID/ack' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"ack_ref": "TICKET-123"}'

Idempotent on the pair of output id and your reference. Sending it twice is safe.

Working the queue from code

curl 'https://api.dmzagent.com/v1/reviews?state=waiting&limit=50' \
  -H 'Authorization: Bearer YOUR_API_KEY'
curl -X POST 'https://api.dmzagent.com/v1/reviews/REVIEW_ID/claim' \
  -H 'Authorization: Bearer YOUR_API_KEY'
What happens when nobody claims a review?
It stays in the queue. Set an escalation rule to tell a second person after a period you choose.
Can a review be reopened?
A closed review stays closed. The event that caused it can fire a new rule, which opens a new review with its own record.
What happens when no acknowledgment arrives?
The decision record marks itself failed after the window set on the rule, and the failure is written to the logbook.
Ask the assistant to wire this in →Open your organization