Reports Processing Time

In the following table you may find processing duration measurements taken based on a variety of test cases for each endpoint. This information can assist you when planning the utilization of Placer API.

Retry triggering

The system is built in a manner that it uses a caching mechanism for reports. As reports producing duration may take a while the system will first verify the reports caching. If the report is found then it will be immediately returned in the response. Otherwise, you will be getting the indication of IN_PROGRESS response (http-code=202) and would be asked to re-trigger the same report for receiving the full report. It is recommended to be advised of the duration estimates above when planning the retry mechanism when utilizing reports’ endpoints.

Please note, that initially, the calls which ended up with IN_PROGRESS response (http-code=202) are deducted from the quota and subsequently reimbursed. A process responsible for this operation occurs once an hour.

⏱Processing duration statistics

🚧

Avoiding Timeout(Http-code=504)

The Visit Trends Reports endpoint generates reports for up to 100 entities based on the requested granularity (DayWeek/Month). Responses may take longer to process due to the potentially large amount of data, resulting in heavy responses.

Using the Visit Trends Reports endpoint for requesting reports for 100 entities with a date range longer than 1 year is currently unsupported.

Timeouts may also arise when employing other granularities, depending on the entities in use. In such instances, consider narrowing the time frames, using longer granularity, or reducing the number of POIs in the bulk query.

⏱Processing duration statistics for Nearby activity reports

Certain properties exclusively accommodate Nearby Activity reports due to their location in dense areas, multistory buildings, or similar settings where visitation processing is not comprehensive. For these properties, visitation insights are computed using a radius ring to identify nearby visits within a specified distance from the property. You can customize the radius ring by setting a distance ranging from 100 ft to 1000 ft in the nearbyRadius parameter when it is available.

When generating a Nearby Activity report (including the nearbyRadius parameter setting), processing durations may vary compared to running standard property reports.

Below, you'll discover the processing durations for Nearby Activity reports: