Report stuck in IN_QUEUE for 24+ hours – GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL

[humzamanzoor]

Hi,
I’m facing an issue where requests for the GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL report remain in IN_QUEUE for more than 24 hours and never move to IN_PROGRESS or DONE.

The strange part is that the same code and parameters work normally for some seller accounts, but for others, the report gets stuck indefinitely. Other report types and API calls for these sellers work fine, so the authentication and integration setup seems correct.

At this point, I’m trying to understand whether this is:

• an SP-API internal issue affecting specific seller accounts,
• related to data volume or backend throttling,
• or something that requires cancelling and re-requesting the report.

If anyone has experienced this or if Amazon can confirm whether this is a known issue, I’d appreciate guidance on the recommended next steps.

Thanks!

[ritikacd]

Hi @humzamanzoor

Currently, we haven't received alerts indicating an issue. Report generation times can vary based on the report size, system load, and the number of processed or queued reports. If reports are taking a longer time than expected, you may want to try reducing the date range.
Additionally, report type rate limits are shared at the Seller Partner level. This means that if a seller submits the same report through multiple applications or via seller central, all requests go into a single queue and are processed sequentially. You may want to confirm with the seller whether they are also submitting this Order report through Seller Central.

If the issue persists, please reach out to our developer support team. They have access to detailed logs and can help troubleshoot more effectively.

Thanks,
Ritika

[humzamanzoor]

I checked with the sellers, and they were not submitting the reports when this problem occurred. The point is, this issue came for 2 to 3 days, and then everything went fine. I myself monitored a report for that specific seller; it took more than 36 hours. However, now the issues seem to have resolved by itself, let's see if it comes again or not.

Thanks for your help and answer :)