Editing a mission creates or changes a draft. Live triggers use the published version until you publish a new version.

​
Before publishing

Review the trigger, Connected Accounts, destinations, required fields and error paths. Test with representative sample data. Confirm the expected output and check that write actions reached the intended test resources.

​
Publish

Open the mission in the builder and choose Publish. Resolve any configuration errors that prevent publishing. The published version is a snapshot of the configuration you reviewed.

​
Enable or disable

Use the mission’s enabled/status control to allow or stop new trigger invocations. Publishing and enabling are different operations. Disabling a mission does not undo changes an earlier run made in an external app. After enabling, invoke the real trigger or wait for its scheduled time. Open Run history and verify the first live run. A successful builder step test alone does not prove that the trigger receives live events.

​
Change a live mission

Make the change in its draft, test the affected steps, then publish the new version. See version history. When a change affects recipients, approval rules or customer records, arrange the appropriate review before enabling it. Native sensitive-project publishing approvals are an optional upstream paid control and are excluded here. Business approval steps inside a mission are covered in human review.