What the message means
When Luminous pushes a fulfillment order to ShipStation and ShipStation responds that it is temporarily unavailable or that too many requests arrived at once, Luminous writes a note to the order such as:
ShipStation transient failure (HTTP 429), deferred for retry. Too Many Request
or a variant referencing HTTP 502, 503, or 504. These codes all mean ShipStation was momentarily busy — not that the order data is wrong or that the push will never succeed.
What Luminous does automatically
- The fulfillment order is not marked as Error. It stays in its normal pushable status.
- The next scheduled auto-push run (which runs every few minutes) picks the order up and tries again.
- If the retry succeeds, Luminous clears the temporary note and the order proceeds normally.
- No alert fires and no manual action is required in the typical case.
When you might need to act
| Situation | What to do |
|---|---|
| The note has been on the order for more than an hour and the status has not advanced | Manually re-push the fulfillment order from its detail page (Actions → Push to ShipStation). If it fails again immediately, check ShipStation's status page for an ongoing outage. |
| Many orders show this note at the same time | This usually indicates a large push burst hit the rate limit. Luminous will retry them in staggered fashion; give it 15–30 minutes before manually intervening. |
| The status did advance to Error (rather than staying pushable) | This can happen on orders created before the September 2026 auto-recovery fix. Contact support for a bulk re-push. |
Background
ShipStation limits how many API calls can be made in a short window. During large push runs (end-of-day waves, multi-warehouse bursts), Luminous can temporarily exceed this limit. The auto-recovery behavior described above was made permanent for all accounts in September 2026.