Job Types
Each job has a type that identifies the operation it represents. The detail view of a job — what information it shows and what actions are available — depends on its type.
In the job list, the Job column shows the name of the particular run (for example Sync Agent Gateway); the type is shown in the job detail. Types without a dedicated view show a generic list of their phases.
| Type | Description |
|---|---|
| Permission Settings | Applying permission changes to a resource |
| Create Environment | Creating a new environment |
| Delete Environment | Deleting an environment |
| Custom Template Dry Run | Running a dry run of a custom component template (Agent Template Dry Run for custom agent templates) |
| Custom Template Dry Run Delete | Deleting a custom component template dry run |
| Resource Labels | Applying label changes across resources |
| Deploy Application | Deploying an application package to one or more target environments |
| Deploy Agent Swarm | Deploying or redeploying an agent swarm package to an environment and registering its agents in the Agent Gateway |
| Undeploy Agent Swarm | Removing an agent swarm from an environment and cleaning up its Agent Gateway registrations and tokens |
| Synchronize Agent Gateway | Synchronizing MCP server registrations in the Agent Gateway after a data plane changes |
| Update Service Account | Changing a service account's owner, permissions or permission mode |
Common behavior
- Jobs that work on the same resource (for example deployments of the same agent swarm to the same environment) never run in parallel — they wait for each other and run in the order they were requested.
- A job that waits longer than 24 hours is cancelled automatically, unless it is in a phase that cannot be cancelled.
- Failed jobs can be retried and running jobs cancelled — as a whole, or for a single target where the job type supports it.