Separate retryable Merchant API failures from final product errors.

Exact migration problem: old bulk jobs often retry too broadly, hiding Merchant API validation failures, permission errors, stale queue payloads, or quota pressure.

Legacy pattern: retry every status >= 400 or send product writes with unbounded Promise.all after replacing customBatch.

Merchant API target pattern: retry transient 429 and 5xx failures only, cap concurrency, dead-letter final validation and permission failures, and reconcile every product write.

Scanner rule IDs: merchant-api-retry-all-4xx, merchant-api-custombatch-promise-all-unbounded, merchant-api-dynamic-client-not-verified.

Common failure cases: invalid payloads retry until worker timeout, permission errors become generic queue failures, and catalog-wide retries make quota diagnosis harder.

Validation checklist: run staging replay with invalid payload, clean product, transient retry simulation, queue-drain evidence, and redacted CI artifacts.

Related checks: customBatch migration, CI integration, Sample report, Methodology, Security, and Run free scan.

Run free scan - no signup required See a complete sample finding View pricing