Details of request “Gazebo usage

Event history

This table shows the technical details of the internal events that happened to this request on OPRAmachine. This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Be careful! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on OPRAmachine. How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand FOI law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type details created_at described_state calculated_state last_described_at link
1369787  sent    2025-08-18 14:38:53 -0400  waiting_response  waiting_response  2025-08-18 14:38:53 -0400  outgoing  
1369807  response    2025-08-18 15:42:38 -0400        incoming  
1369808  response    2025-08-18 15:42:38 -0400        incoming  
1373357  followup_sent    2025-08-22 19:54:01 -0400        outgoing  
1373358  response    2025-08-22 19:54:37 -0400    waiting_response  2025-08-26 18:02:18 -0400  incoming  
1375908  status_update    2025-08-26 18:02:18 -0400  waiting_response  waiting_response  2025-08-26 18:02:18 -0400   
1376445  response    2025-08-27 17:48:50 -0400        incoming  
1379421  overdue    2025-08-28 00:00:00 -0400         
1376978  response    2025-08-28 09:17:12 -0400    partially_successful  2025-11-19 13:59:31 -0500  incoming  
1378242  status_update    2025-08-29 19:00:39 -0400  waiting_response  waiting_response  2025-08-29 19:00:39 -0400   
1404571  followup_sent    2025-09-13 23:24:34 -0400        outgoing  
1409213  very_overdue    2025-09-17 00:00:00 -0400         
1418760  followup_sent    2025-09-25 08:43:04 -0400        outgoing  
1468433  status_update  described_state  2025-11-19 13:59:31 -0500  partially_successful  partially_successful  2025-11-19 13:59:31 -0500   
1614596  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614597  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614598  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614599  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614600  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614601  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614602  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614603  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614604  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614605  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614606  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614607  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614608  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         
1614609  edit metadata  allow_new_responses_from  2026-05-20 03:45:08 -0400         

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by OPRAmachine for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.