Request operations
Event history details
Technical delivery, response, and status events for Legal basis and status of announced monitoring of “indecent behaviour”. Use this page when you need the underlying chronology rather than the public request summary.
Technical event log
This table shows the internal events that Urumuri recorded for this request, including outgoing mail, incoming responses, and user-set status changes.
| id | event_type | details | created_at | described_state | calculated_state | last_described_at | Link |
|---|---|---|---|---|---|---|---|
| 16 | sent | 2026-08-10 14:27:14 +0200 | waiting_response | waiting_response | 2026-08-10 14:27:14 +0200 | outgoing | |
| 34 | overdue | 2026-08-14 00:00:00 +0200 | |||||
| 58 | very_overdue | 2026-09-03 00:00:00 +0200 | |||||
| 75 | followup_sent | 2026-09-21 11:51:42 +0200 | outgoing | ||||
| 76 | status_update | 2026-09-21 11:52:32 +0200 | waiting_response | waiting_response | 2026-09-21 11:52:32 +0200 | ||
| 77 | status_update | 2026-09-21 11:55:24 +0200 | waiting_response | waiting_response | 2026-09-21 11:55:25 +0200 | ||
| 88 | followup_sent | 2026-10-07 15:33:50 +0200 | outgoing |
How to read this page
Here described means the status explicitly chosen by a user for the request. Calculated state is inferred by Urumuri for the events between those user decisions.
Use these records carefully. To compare response performance reliably, you need context about user behaviour, institutional practice, and how different request states are applied.