Workflows

Composite agent-runner execution chains.

This screen belongs to the Router deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

If Preview is available, open /workflows.
Click Create workflow and enter docs-pipeline.
Create it, refresh and check its name and version.
Configure and run the execution plan through the supported agent-runner API; this form does not expose it.

Every control and its meaning

Control / parameter	Values, units and effect
Название / Name	Required; used to identify the workflow. Example: docs-pipeline.
Версия / Version	Displayed with update time. The current console form contains a name and has no graphical chain editor.
Preview	Normally hidden and requires the agent-runner runtime. Creating a record does not prove execution.

Verify the result

Only a completed runtime test confirms that the chain executes.

Errors, disabling and reverting changes

If the runtime is disconnected, arrange setup with the operator. Cancel closes the form; preserve the plan and referencing calls before deletion.

Detailed security settings · Traffic analysis · FAQ · All application sections