3 mins READ

What happens when you submit an outbound change set, and how it reaches the destination.

Overview

Q: How does a Move change set reach the destination?

For a Move, on submit the platform sends the packaged bundle straight to each connected environment you chose. It transfers the bundle securely and tells the destination it has arrived, where it appears as a new inbound change set in Pending status, ready for review and approval. You don't hand any files around — the connection between the environments carries it. The source environment then tracks each destination's progress (received, approved, deployed) so you can see how the promotion is going from where you submitted it. Where: Outbound change set › Move (push to connected environment)

Q: Can I change a change set after I submit it?

No — once submitted, an outbound change set is read-only in the source environment. Its assets, versions, and settings are locked so that what each destination received can't change underneath them. If you need to send further changes, create a new change set (you can clone the old one to start from the same selection). You can delete a submitted change set — for a Move, that withdraws it: any destination copy still sitting in Pending is Cancelled and can no longer be actioned there. This immutability is deliberate: it keeps a clean record of exactly what was promoted and when, which matters for auditing a release. Where: Outbound change set (after submit)

Submitting moves the change set from Draft to Exporting while the platform does the work, then to Submitted when it's ready. Behind the scenes it: gathers all the selected assets plus their dependencies, takes a snapshot of each at the chosen version, records who owns and shares them (so that's preserved in the destination), and packages everything into a single encrypted bundle stored securely — including any files an asset carries (an agent skill's uploaded files travel with it and are re-created in the destination; a file shared by two assets is packaged once). From there it's either pushed to your connected environment(s) or made available as a file, depending on the change set's type. Once it's Submitted, the contents are fixed.

Where: Outbound change set › Submit

How an Export change set works

For an Export, the platform packages the change set into an encrypted, password-protected file instead of pushing it (a password must be set on the change set before it can be exported). Once it's Submitted, an Export action on the outbound list downloads the file; you transfer it yourself, then in the destination environment use Import Change Set under Inbound and upload it (supplying the password) to create the inbound change set. Use Export when the two environments aren't connected, when policy requires a manual hand-off, or for an offline/air-gapped move. The review, approval, and deploy steps in the destination are the same as for a Move once it's imported.

Where: Outbound change set › Export (file)

FAQs

How does a Move change set reach the destination?

For a Move, on submit the platform sends the packaged bundle straight to each connected environment you chose. It transfers the bundle securely and tells the destination it has arrived, where it appears as a new inbound change set in Pending status, ready for review and approval. You don't hand any files around — the connection between the environments carries it. The source environment then tracks each destination's progress (received, approved, deployed) so you can see how the promotion is going from where you submitted it.

Where: Outbound change set › Move (push to connected environment)

Can I change a change set after I submit it?

No — once submitted, an outbound change set is read-only in the source environment. Its assets, versions, and settings are locked so that what each destination received can't change underneath them. If you need to send further changes, create a new change set (you can clone the old one to start from the same selection). You can delete a submitted change set — for a Move, that withdraws it: any destination copy still sitting in Pending is Cancelled and can no longer be actioned there. This immutability is deliberate: it keeps a clean record of exactly what was promoted and when, which matters for auditing a release.

Where: Outbound change set (after submit)

Last updated : 31 August 2026, 12:19 PM

Submitting and sending a change set

Overview

How an Export change set works