description of up to 500 characters.
The app calls a trigger a loop. The API creates loops that start on a deploy or a schedule, and that run flows or Run AI. It can’t create a loop that starts on a pull request or a QA Wolf event, and reports one with a configuration.kind of advanced.
Deployment conditions
Every condition supplied must match. A trigger with no conditions fires on every deployment the workspace receives.
Patterns ignore case. In a pattern:
*matches any run of characters,/included.release/*matchesrelease/1.2andrelease/1.2/hotfix.{a,b}matches any one of its comma-separated options.{main,hotfix}matches either branch, and an option can hold*, as in{release/*,hotfix/*}.- A leading
!matches every value the rest of the pattern doesn’t.!{main,hotfix}matches every other branch. - Every other character matches only itself,
?,[,],(,)and.included. A brace with no comma, such as{owner}, is literal too.
!.
environmentPattern matches the name of the QA Wolf environment the deployment resolved to, not the name your pipeline sent. See Deployments.
Schedule
dayOfWeek and daysOfWeek are different fields for different cadences. dayOfWeek is a single day and belongs to a weekly cadence, which fires on that one day. daysOfWeek is a list and belongs to an hourly or daily cadence, where it narrows an otherwise every-day schedule to the days you name. Neither field is accepted by the other’s cadence.nextScheduledAt.
Action
An action names at least one flow or tag, or is a
generativeSuite or a startAgent. A startAgent action refuses flowIds, tagNames, investigateFailures, and runConcurrencyLimit. A generativeSuite action:
- Refuses
flowIdsandtagNames. - Is only valid on a deployment trigger.
- Matches a deploy that isn’t tied to a pull request, but doesn’t run on it: the run outcome is
did-not-runwith reasonno-pull-request. See PR testing for what ties a deploy to its pull request.
Paused
SendisPaused: true to trigger.create to create a trigger that never fires until trigger.resume. A paused trigger still fires by hand through trigger.runNow.
A paused trigger’s conditions aren’t checked. It still records a verdict for each deployment: not-considered, with reason trigger-paused.
Resuming brings back the same configuration. A resumed schedule’s nextScheduledAt moves to its next upcoming slot, and slots missed while paused don’t run.
Reading a trigger back
configuration— the deployment or schedule shape, for a trigger that runs flows. A trigger that runs AI, or that starts on a pull request or a QA Wolf event, reportsadvancedhere.definition— the full configuration, a trigger that runs AI included, in the shapetrigger.updateaccepts back. Absent for a trigger that starts on a pull request or a QA Wolf event.pausedReason— why QA Wolf paused a trigger that runs AI:no-ownerwhen no person owns it, orowner-left-teamwhen its owner is no longer a member. A person resumes it by selecting Make me the owner in the app.