Amazon SP-API FBA Report Generation Failures and Rate Limit Issues in Celigo

Hello,

I am facing issues while generating the Amazon SP-API report GET_FBA_FULFILLMENT_REMOVAL_SHIPMENT_DETAIL_DATA through Celigo. We are generating the report for a one-week date range using the dataStartTime and dataEndTime parameters.

We are using Celigo's Async Helper to check the report status and retrieve the report once it is ready. Currently, both the initial wait time and polling interval are configured to 5 minutes. However, we are encountering a QuotaExceeded (429) rate-limit error, and the report generation is also failing with a FATAL status.

Could you please advise on the following?

  1. What could be causing these errors, and how can we resolve them?

  2. Is there a recommended date range for generating this report, or should we try generating it one day at a time?

  3. Are the current 5-minute initial wait time and polling interval appropriate, or would you recommend different settings?

  4. Are there any specific limitations or best practices for using the Async Helper with this report?

Your guidance would be greatly appreciated.

Thank you!

Hi Prajakta,

Are you generating other reports besides this at the same time? On which part are you getting the qouta error? Is it when you are getting the report ID or the reportDocumentID?

Hello Calvin,

We are currently developing the following two flows:

  • DF#1: Sync Removal Order from Amazon to NetSuite

  • DF#2: Sync Removal Order Shipment from Amazon to NetSuite

Neither flow has been scheduled yet.

We have successfully tested DF#1 and can generate the report using an initial wait time of 1 minute and a poll time of 2 minutes. We are not currently testing or running this flow.

However, for DF#2, we are unable to generate the report even after increasing the initial wait time to 3 minutes and the poll time to 5 minutes.

Our eventual plan is to schedule both flows to run once daily.

Could you please advise if there are any additional considerations or recommended wait and poll time settings for DF#2 to help resolve this issue?

Hi Prajakta,

I do not think adjusting the poll time will fix this. Can you try running the flow and send us the Amazon connection debug log. I just want to see how many request it did before it reached the quota.