GOOD TO KNOW

Background automations

Updated October 22, 2026 · 2 min read
About every 3 minutes DevFlow looks at your open pull requests and runs the automations you turned on — even with no Jira tab open.

01How it works

1
It runs inside Chrome
While Chrome is open with the extension installed, a run starts about every 3 minutes. You don’t need a Jira tab or the panel.
2
It uses your saved settings
Each run reads the settings you last saved, per repository. Turn an automation on and it takes part in the next run.
3
Only your own pull requests
Each run looks at the open PRs you authored. Teammates’ PRs are never merged, fixed or moved by your DevFlow.
4
Each step happens once
DevFlow remembers what it already did, so a later run doesn’t merge, remind or move the same thing twice.

02What needs an open Jira tab

Most automations need only Chrome. A few need more.
AUTOMATIONWHAT IT DOESNEEDS
Auto-mergeMerges your PRs once your rules are met.Chrome
Auto-fixFixes reviewer comments with your AI CLI.Chrome + Desktop
PipelinesRestarts failed pipelines and sends pipeline notifications.Chrome
Jira status syncMoves the issue on pull request events.Chrome
Sprint status syncRuns every 3 minutes while the tab is open.Jira tab
Actions you click in the panel, such as creating a branch, need the Jira tab too.

03Good to know

Some actions start a run at once
Marking a PR ready for review in the panel starts a run right away instead of waiting.
Auto-merge goes last
In each run auto-merge comes after auto-fix, so a PR that’s being fixed is never merged from under it.
Errors stay contained
A failure in one repository or PR never stops the others. Results land in the background automation log, except background auto-fix runs, which don’t log yet.
Rate limits pause, not retry
When GitHub or GitLab limits your requests, DevFlow pauses briefly. Skipped work happens on a later run.