One indexed statement instead of a per-patient walk. matchMetadata is a jsonb containment match on each trigger's own labels — Signals does not interpret the keys, so a caller chooses labels that make the sets it wants to move addressable.
A narrower pattern reaches fewer triggers. That is how one write updates a whole group while leaving per-patient exceptions untouched, provided the caller labelled them differently in the first place.
codes narrows on the trigger's own code column, and is REQUIRED when the update writes logic or constants. Those are written verbatim to every matched row, and a label pattern spans every code the caller has stamped — so an unscoped rule write puts one metric's rule onto every other metric's trigger and still returns a healthy matched. A metadata-only update may omit it, since relabelling is not code-specific.
CHECK matched. Zero means the pattern selected nothing — usually unlabelled triggers rather than a failed write, and it is not reported as an error.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
The update carried no changes, or the payload failed validation.
Missing, malformed or unrecognised Basic credentials.
Authenticated, but the client's role does not permit this, or it is not attached to the patient.