Webhooks
What the Screen Is For
Investigate saved provider messages and request another processing attempt.
What It Shows and Lets People Do
The message table exposes endpoint, verification, processing standing and receipt time. Detail includes the saved digest and derived events. Replay uses saved material and creates new processing records rather than mutating the earlier message into a queued message.
States and Errors
The Library rejects entry without its read authority. Shared loading and error presentation handles data reads; mutation controls are gated separately. A visible control can still be refused by the API’s independent authorization or lifecycle validation.
Patterns It Must Respect
LibraryPage with breadcrumb navigation. ReadState, Empty and shared error presentation for data reads. The Library access boundary controls entry; each action retains its implemented permission gate. Received-message table and replay confirmation dialogs.