Details of request “Failed Trade Deliveries (FTDS)

Event history

This table shows the technical details of the internal events that happened to this request on AccessInfoHongKong. 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.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on AccessInfoHongKong. 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
15979  sent    2022-11-03 12:58:49 +0800  waiting_response  waiting_response  2022-11-03 12:58:49 +0800  outgoing  
15981  response    2022-11-03 13:00:04 +0800    waiting_response  2022-11-06 15:11:55 +0800  incoming  
16051  status_update    2022-11-06 15:11:55 +0800  waiting_response  waiting_response  2022-11-06 15:11:55 +0800   
16102  response    2022-11-10 16:55:44 +0800    not_held  2022-11-10 17:53:02 +0800  incoming  
16103  status_update  described_state  2022-11-10 17:53:02 +0800  not_held  not_held  2022-11-10 17:53:02 +0800   
16104  followup_sent    2022-11-10 17:53:35 +0800        outgoing  
16106  response    2022-11-10 18:00:08 +0800        incoming  
18963  edit metadata  allow_new_responses_from  2023-05-11 11:45:17 +0800         
18964  edit metadata  allow_new_responses_from  2023-05-11 11:45:17 +0800         
18965  edit metadata  allow_new_responses_from  2023-05-11 11:45:17 +0800         
18966  edit metadata  allow_new_responses_from  2023-05-11 11:45:17 +0800         
18967  edit metadata  allow_new_responses_from  2023-05-11 11:45:17 +0800         
18968  edit metadata  allow_new_responses_from  2023-05-11 11:45:17 +0800         
18969  edit metadata  allow_new_responses_from  2023-05-11 11:45:17 +0800         
30628  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30629  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30630  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30631  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30632  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30633  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30634  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30635  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30636  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30637  edit metadata  allow_new_responses_from  2025-05-02 11:45:58 +0800         
30638  edit metadata  allow_new_responses_from  2025-05-02 11:45:59 +0800         
30639  edit metadata  allow_new_responses_from  2025-05-02 11:45:59 +0800         
30640  edit metadata  allow_new_responses_from  2025-05-02 11:45:59 +0800         
30641  edit metadata  allow_new_responses_from  2025-05-02 11:45:59 +0800         

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 AccessInfoHongKong 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.