On this page

Show all

Help Center/ Content Delivery Network/ FAQs/ Cache Purge and Prefetch/ Why Does a Prefetch Task Remain in the Being Processed Status for a Long Time?

Why Does a Prefetch Task Remain in the Being Processed Status for a Long Time?

Updated on 2024-04-17 GMT+08:00

View PDF

Possible causes:

The task was submitted during a peak hour, so it is still in the queue.
You are prefetching a large number of files. Prefetch will pull content from the origin server so prefetching a large number of files may consume all of the bandwidth available for your origin server. You are advised to:
- Divide the prefetch tasks into batches.
- Prefetch files during off-peak hours, for example, at night.
- Increase your origin server bandwidth.
The task has been completed but the status is not refreshed on the console. Refresh the console page and check again.

Parent topic: Cache Purge and Prefetch

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel