Skip to main content

Settings Reference

The values fixed in Project in the Marketplace edition. Values that are the same as in the SaaS edition are not listed. For items not listed, see the SaaS edition's Settings Reference. Item names follow what the screen shows.

Project​

ItemValue
Default typeWorkflow (Cycle in the SaaS edition)
How to create it“Build it myself” only. There is no creating through consultation with the AI or by guided setup
Number of projectsNo limit
Retries per step (failed / timed out)The screen lets you choose 0 to 10, but on a registered agent's step up to 2 take effect. It retries automatically only when the contract's “Effect on external systems” is “Read only” or “Writes (safe to retry)”, and only for failures where what happened is known. Once the retries are used up, the case closes as failed (Trigger Guide)

Steps​

ItemValue
Agents that can be placed on steps (workflows)Only certified registered agents with a workflow contract registered in the admin console
Agents that can be placed on steps (cycles)Registered agents enabled in the admin console (agents used in chat). No contract or certification is needed
Lanes, Run at the same time, Destination options, destinations by resultNot available. Refused on saving or starting
Handling of results (when not allowed by rules, when the agent reports it could not finish)Not on the screen. It runs with a fixed handling (Trigger Guide)

Step settings (workflows)​

ItemValue
ParametersOf the contract's settings items, those of type string, integer, number, yes/no and choice can be changed on the screen. Only the items you enter a value for are saved; items left blank keep the agent's default values. Items of other types are settled by the administrator in the contract
ConnectionsFor each connection slot in the contract, choose one of this project's connectors. Only the connections the administrator allowed for the slot can be chosen
Input bindingsBind the output of an agent on a preceding step as this agent's input file. Files not bound are passed when the case starts
Execution limitSettled by the contract. 900 seconds by default. 0 means no limit (up to the deployment's limit; 24 hours by default). It cannot be changed in the project

Environment variables (cycles)​

ItemValue
NumberUp to 32 per placement
SizeNames and values totalling up to 16 KiB
NameStarts with an uppercase letter and uses uppercase letters, digits and _, up to 64 characters
Names that cannot be usedReserved names (names starting with ASTER_ or MP_, PATH and so on), names registered as secrets for the agent, names the administrator has blocked from change

Review steps​

ItemValue
Review method“Stop and wait for a decision” or “Wait for an external condition”
When the deadline passesNot decided automatically. Even after the deadline it waits for the reviewers' decision, and notifies that it is overdue
Destination optionsNot available
External conditionOne kind: “GitLab MR merged”
Interval for observing the external condition300 seconds. When a webhook from the connector is received, it is also read again at that point
External-wait webhook secret16 to 255 characters. The saved value is not shown

Cases (workflows)​

ItemValue
Size of artifactsUp to 20 MiB per file. Up to 100 MiB and 100 files in total per execution
Artifacts that can be edited on the screenText up to 1 MiB
When the settings and artifacts can be changedOnly while awaiting review. They cannot be changed while running or in a finished case
Starting a case, editing settings and artifacts, cancellingOwners only

Triggers​

ItemValue
Start by emailNot available
External APIOnly the endpoints called with a service account token (API Reference). Parameters cannot be passed at the start of a case started from the external API or a time trigger
Overlapping sweeps (cycles)A round that comes while the same placement is running is skipped (not piled up)
Late sweeps (cycles)A round more than 5 minutes past its schedule is recorded once as skipped, and it moves on to the next scheduled time
Before the same placement's next start (cycles)60 seconds after the previous execution ends. Sweeps during that time are skipped; webhook calls wait and then start
Webhooks (cycles)Calls received are not merged; each is passed to the same placement one at a time, in order. Up to 20 can wait per placement (beyond that, 429 queue_full). A call more than 24 hours past being accepted is not started