Skip to content

Polling & dedup

Linear, Jira and GitHub triggers find work by polling: they run their query on an interval and start a run for each matching issue they haven’t processed yet. This page covers the mechanics shared by all three.

Setting Value
Poll every (seconds) default 120
Minimum 15 (smaller values are treated as 15)
Scheduler resolution Jimothy checks every 5 seconds whether a trigger is due
Issues per poll 50 (Linear and GitHub: most recently updated; Jira: in your JQL’s ORDER BY)

A poll that’s still in progress isn’t started again. Disabled (paused) triggers don’t poll. Polling starts when the app launches and continues while Jimothy sits in the tray with its window closed.

Faster polling means more API requests; for near-instant starts, use webhooks in addition to a relaxed poll interval.

Each trigger remembers the issues it has already started runs for, keyed by issue key (ENG-123, WEB-45, web-app#42, or the webhook key), with the run it started and the issue’s “updated” time. An issue that’s already been processed is skipped on every later poll, so a matching issue starts one run per trigger, no matter how long it keeps matching.

Things to know:

  • Dedup is per trigger. Two triggers that both match an issue each start a run.
  • Dedup applies to webhook deliveries as well, so an issue that arrives by webhook and then shows up in a poll runs once.
  • Schedule triggers don’t dedup; every firing is a new run.
  • A run’s success or failure doesn’t matter: a failed issue isn’t retried automatically. Use Retry on the run, or forget the issue in Processed issues.
  • Deleting a run doesn’t clear its issue. The issue stays processed until you forget it.
  • Dedup state lives in trigger-state.json in the data folder and survives restarts.

There are three ways to run a processed issue again:

Processed label is an optional field on Linear, Jira and GitHub triggers. It’s blank (off) by default; the placeholder suggests jimothy-ran. With it set, the label in your tracker decides whether an issue runs again, so you can re-run an issue without opening Jimothy.

  • When Jimothy starts a run for an issue, it adds the label to the issue. GitHub and Linear create the label if it doesn’t exist.
  • Issues that have the label are skipped.
  • Remove the label in the tracker and the issue runs again on the next check, once its previous run has finished (succeeded, failed or cancelled).
  • Label matching ignores case.

An issue only runs again after Jimothy has seen the label on it. If adding the label fails (for example, the account can’t edit labels), the trigger shows an error such as:

Couldn't add the "jimothy-ran" label to WEB-45, so it won't run again until the label is added and removed: …

This keeps an issue whose label never got added from starting a run on every poll.

Issues the trigger processed before you set the label don’t have it, so they don’t run again on their own. To re-run one, add the label, wait for a check, then remove it. Or Forget it in Processed issues.

With a processed label set, Run again when a processed issue is updated is hidden. The editor shows With a processed label, the label decides when an issue runs again.

Saving the trigger is rejected when:

  • the trigger is a Jira trigger and the label contains spaces (Jira labels can't contain spaces; use something like "jimothy-ran");
  • on Linear or GitHub, the processed label is also one of the labels the trigger picks issues by, so every issue would be skipped.

On Jira, don’t make the JQL select the processed label (for example labels = jimothy-ran): every matching issue would be skipped. You can exclude it, which also keeps processed issues out of the 50 issues per poll:

labels = jimothy AND labels != jimothy-ran AND statusCategory != Done ORDER BY created ASC

On GitHub, webhook triggers also act on unlabeled events, so removing the label re-runs the issue as soon as GitHub delivers the event. See GitHub.

A trigger set to Add to a board follows the same rules, with the issue’s board card in place of a run: each issue is added once, the processed label is added when the card is added, and with Run again when a processed issue is updated an update is ignored while the card is waiting, running or in review. An issue added again after its card finished goes back to the board’s Inbox.

This option is only shown when Processed label is blank.

Turn on Run again when a processed issue is updated to start a new run when an already-processed issue changes. A new run starts only when all of these are true:

  1. the issue still matches the trigger’s filter;
  2. its “updated” time (Linear updatedAt, Jira updated, GitHub updated_at) is later than when it last started a run;
  3. the previous run for that issue has finished (succeeded, failed or cancelled). While a run is still active, updates are ignored.
Where Control What it does
Trigger editor Preview matching issues Runs the query with the unsaved settings and shows how many issues match right now and the first eight (key, title, state, labels), or the exact error. Doesn’t start runs. For schedules this button is Validate and checks the cron expression.
Trigger card Check now Polls immediately, ignoring the interval, and starts runs for new matches.
Trigger card Eraser button — Processed issues Lists the issues the trigger has processed, and lets you forget one or all of them. See Processed issues.
Trigger card Toggle Pauses or resumes the trigger.

Trigger cards are on a project’s Triggers tab (or the all-projects list: All triggers in the ⌘K palette). Each shows its status pill (live, error or paused), a one-line summary of its filter, the pipeline it runs, the account, the poll interval, when it last checked, how many runs it has started (for a board trigger: which board, and how many issues it has added to it) and how many issues it has processed.

Click the eraser button on a trigger card to open Processed issues. It lists every issue the trigger has started a run for, newest first:

  • the issue key;
  • when it ran;
  • a link to its run with the run’s status, or run deleted if you’ve deleted the run; for a board trigger, the card’s status instead (card waiting, card done…), or card removed;
  • labeled when the trigger has a processed label and Jimothy has seen it on the issue.

Forget removes one issue from the list. It runs again on the next check if it still matches the trigger’s filter and, with a processed label, doesn’t have the label. Forget all (shown when there’s more than one issue) clears the whole list and the trigger’s runs started count, so every issue that matches right now (and, with a processed label, doesn’t have it) starts a run on the next check.

Deleting a run doesn’t remove its issue from this list.

When a poll fails (bad credentials, an invalid JQL query, a missing repository, network errors) or a write-back fails:

  • the trigger card shows the error in red and the pill turns error;
  • the sidebar’s Triggers item shows a red !;
  • the Dashboard’s Triggers card shows the error message;
  • a Trigger errors (trigger.error) notification is sent, but only when the message changes, so a trigger failing the same way every two minutes doesn’t flood you.

The next successful poll clears the error. Paused triggers don’t show errors.

Other errors you may see:

Error Cause
Trigger "X" has no linear account. Pick one in the trigger settings. The trigger’s account was not set.
Account "Y" is a jira account, not linear The trigger points at an account of another platform.
Jira trigger needs a JQL query / GitHub trigger needs owner and repo Required fields are empty.
Trigger "X" — Its pipeline no longer exists The pipeline the trigger runs was removed. (Jimothy won’t let you delete a pipeline a trigger uses, so this is rare.)
HTTP 401 Unauthorized from api.linear.app: … The key or token was revoked or expired. Re-sign in under Settings → Accounts & integrations.