MismatchReportedEvents, groups similar reports (same partner row, same suggested correction), drafts a proposed resolution, and files it as a pending item.
What you’ll build
An agent that:- Subscribes to
MismatchReportedEvent. - Reads the existing open mismatch reports for the same partner row.
- If there’s a similar one, marks them as a group.
- Drafts a 1-2 sentence proposed resolution (e.g. “All three reports converge on referenceHotelId
ref_01J...— agree.”) and posts it as a pendingMISMATCH_PROPOSED_RESOLUTIONitem.
FIXED or REJECTED — that stays with a human.
Steps
Create the agent
Name: “Mismatch triage”. Goal:
Watch new mismatch reports. Group similar ones, draft a proposed resolution as a pending item. Never mark fixed or rejected.
What a reviewer sees
In Pending → MISMATCH_PROPOSED_RESOLUTION, each item shows:- The grouped mismatch reports (count + links).
- The agent’s proposed resolution text.
- Apply (advances reports to
FIXEDwith the resolution body) / Modify / Reject buttons.
Equivalent API call
Undo
MarkingIN_PROGRESS is undoable (reverts to OPEN) for 7 days from the workspace Undo Center. Filing pending items is undoable via dismiss.
Related
- Agents overview — broader context.
- Audit and undo — what’s undoable.
- Rules and decisions — the mismatch rule group.