Data Queue

When calling a purge or prefetch request, we monitor whether the sent URL has been accepted and sent to our queue. We are not able to provide you with information on whether the purge or prefetch itself was successful. The data queue method is here to help you go through the purge and prefetch results.

Your request receives a timestamp when it has been finished (successfully or not).

url_successful

Amount of successfully proceeded URL. Until the request is finished, this number may increase in time.

url_total

Total amount of URL in a request.

waiting_for_request_id

When enabling the 'purge_first' option on the prefetch method, the urls are saved into the queue twice - first into the purge and then to the prefetch. To ensure the purge is proceeded first, we add the id of the purge request into the prefetch as value waiting_for_request_id. Valid values: null or int.

Your request receives a timestamp when it has been finished (successfully or not).

url_successful

Amount of successfully proceeded URL. Until the request is finished, this number may increase in time.

url_total

Total amount of URL in a request.

waiting_for_request_id

When enabling the 'purge_first' option on the prefetch method, the urls are saved into the queue twice - first into the purge and then to the prefetch. To ensure the purge is proceeded first, we add the id of the purge request into the prefetch as value waiting_for_request_id. Valid values: null or int.