Publishing and environments

Publishing turns your draft into an immutable version. That is what the agent runs from.

Draft and version

	Draft	Version
Does it change?	Yes, you edit it	Never
Does it run?	Only in tests	Yes, when active
How many?	One per agent	As many as you publish

A published version does not change for anything: not by editing, not by credential rotation. If something has to change, you publish a new version.

Publishing

1. Save the draft.
2. Choose the version number, semantic style (1.2.0). It is unique within the agent.
3. Publish.

Publishing validates the whole definition before creating the version. An invalid definition is refused with the step and the reason. That covers the flow's structure, references between values, each step's configuration, limits against the space's ceilings, and the declared resources.

Activating in an environment

A version only runs when it is active in an environment.

Environment	For what	Minimum role
development	Testing for real	People who build
production	Running for real	People who publish

At most one active version per environment. Activating another deactivates the previous one — and the history stays whole.

The full cycle

Draft → Publish → Activate in development → Test → Promote to production

Going to production is not activating again: it is promoting the same version that ran in development. See Promoting and rolling back.

What changes when you publish again

Nothing that is already running. Triggers point to an exact active version; publishing a new version does not move them on its own.

When you activate the new version, the previous one stops being active — and that is what makes the schedule start running the new one.

Differences between the environments

Beyond the required role, triggers behave differently:

In development	In production
HTTP addresses are always temporary	Addresses can be permanent
Schedules always expire	Schedules are durable

This keeps a forgotten test from still firing months later.

Common errors

Message	Meaning	What to do
Version number already used	Each version is unique within the agent	Choose the next number
Conflict on save	Someone else changed the draft	Reload and reapply your change
Refused because a limit exceeds the ceiling	The agent declares more than the space allows	Reduce it, or ask for the ceiling to be reviewed
Refused because a resource is not allowed	A tool or address is not allowed in the space	See Allowed resources
Refused because there is no service account	AI steps require a service account	See Service account

Next steps

• Promoting and rolling back
• Triggers
• Following runs