Skip to main content

Check Order Status

Use order status checks when your main question is order progression:

  • Historical order: "Is this fixed window fully done?"
  • Live order: "Is this order currently caught up?"

For date-level download readiness, use Check availability.

In this context:

  • Live order: an order with future dates still expected to be produced under the current configuration.
  • Recurring orders are always live orders because they renew month to month until recurrence is canceled.
  • Some fixed-window orders can also be live until their time window is fully produced.

Status vs Availability

  • Order status tells you lifecycle progress for the order as a whole.
  • Availability tells you whether specific dates and request settings are ready for download.

In practice:

  1. Check status first to confirm the order has progressed as expected.
  2. Check availability when you need exact date/request download gating.

Dashboard: My Orders

Use My Orders to review live status and the order timeline.

Key statuses:

  • Review: awaiting acceptance.
  • Preparing: setup in progress.
  • AwaitingSatelliteProducts: waiting for source products.
  • Processing, Predicting, ProcessingPredicting: production in progress.
  • Completed: order finished; no additional dates are expected under current settings.
  • UpToDate: live order is currently caught up for dates expected so far.
  • Canceled: order canceled and no longer progressing.

For full UI behavior, see My Orders.

API: Order Details

Use the order details endpoint:

  • GET /api/tasking/orders/details

Read OrderingProcessStatus in the response to determine current progression state for that order.

For endpoint index coverage, see Tasking / order endpoints.

  1. Poll order details and track OrderingProcessStatus.
  2. For fixed-window historical orders, treat Completed as done for lifecycle progression.
  3. For live orders (including recurring), treat UpToDate as caught up for the current cycle.
  4. Before downloading a specific date/output, run availability checks for exact request settings.

Related: