ShipToStore
FLIGHT SUBMISSIONS

Update the package in an existing flight

Keep the audience and routing while preparing the next test release. Available actions depend on the selected flight's current status.

1. Check status and open the flight

  1. Open Flights and select the app.
  2. Select the intended flight and use Refresh. Confirm its audience, rank, current version, status, and any active rollout.
  3. Choose View flight. Open an existing editable draft, or choose Submit new package to begin a new submission when allowed.
Selected flight details with published package version, rollout, audience, and View flight action.
Use the selected-flight details to confirm the target before opening its submission.

If a submission is already processing, or a rollout prevents another update, follow the displayed explanation. Do not recreate the flight just to bypass its status.

2. Replace packages and review release settings

  1. Open Packages and add/replace from your computer or repository.
  2. Verify product identity and a suitable newer version. Review all included architectures and packages rather than assuming that adding one file replaces every older file.
  3. Review Release settings, publication mode, and gradual rollout if used.
  4. Select Save to Partner Center and wait for upload/save completion.

The current editor does not change audience or priority on an already created flight. Those attributes are not part of replacing its package.

3. Submit and follow the outcome

  1. Review the saved draft and choose Submit to start Store processing.
  2. Refresh status and inspect any failure details before attempting another update.
  3. For a manual release, finish the release in Partner Center after certification. For a gradual rollout, monitor and use the offered halt/finalize actions only when appropriate.
  4. Return to Flights to verify the published version and rollout. Test with an account eligible for that flight.

Expected result: the flight's new package is processed and released according to the chosen settings. The separate Retail submission is not automatically updated.

Keep the package and its history

Retain the submitted binary in the package repository. Once testing succeeds, use Promote package to reuse that binary for another flight or Retail.

SSM's timeline records what this workspace has observed; it is not a complete historical archive fetched from Partner Center. The backup/restore preview is intended to preserve that local continuity.

Recreate draft is a recovery action that may discard work. Preserve changes and read the confirmation before using it.