Dismiss a failed expiring queue item

PUT 
/queue/:queueId

Dismisses an overdue queue item so it stops being reported.

Only one change is supported: set request.status to dismissed. The item must be expiring, past its expiry time, and its latest activity entry must be an error (nonzero code). The body may be JSON or form-encoded; the key is the literal string request.status (a flat key, not a nested object).

Required role: admin or superadmin.

A nested JSON object ({"request": {"status": "dismissed"}}) is not understood and returns 501. A second dismissal of the same item returns 403 because it is no longer expiring.

Request

Responses

200

The dismissed queue item.

401

No token, or the token is invalid or expired. The body is {message}: No auth token provided when no token is sent, otherwise the token check's message (jwt expired, jwt malformed, invalid signature, invalid token, jwt signature is required). Send Authorization: Bearer <token> exactly: the server drops the first seven characters of the header and reads the rest as the token, so a different scheme or an extra space fails. If Authorization is absent, the server reads a token field in the body, then a token query parameter, then x-access-token. Routes that validate query fields reject ?token= with 400 InvalidQuery.

403

The item is not an expiring item past its expiry time, or the caller lacks the role.

404

No record has the :id in the path (the id is malformed or unknown). The body is the bare text Invalid <Type> ID (for example Invalid Computer ID, Invalid User ID) with Content-Type text/html; charset=utf-8, not JSON. Some routes return an empty body.

501

request.status is not dismissed, or the latest activity entry is not an error. Empty body.