IBM Quantum (Unofficial) Trigger icon

IBM Quantum (Unofficial) Trigger

Starts a workflow when an IBM Quantum job reaches a terminal state, carrying the failure reason and code when there is one

IBM Quantum (Unofficial) Trigger

AI-generated

Summary

Poll IBM Quantum for jobs in terminal states and start the workflow once for each matching job ID. Choose which terminal statuses to watch, how many recent jobs to scan, and optionally require all listed tags; triggered items include the job data and failure reason fields when available.

Inputs

  • Poll Times — Set the polling schedule, such as every minute, hour, or a custom cron expression. Defaults to every minute.
  • Trigger On — Select any terminal state, canceled, completed, failed, or failed/canceled. Queued and running jobs are ignored and can be picked up on a later poll. Defaults to any terminal state.
  • Jobs to Scan — Maximum number of jobs to inspect per poll, from 1 to 200; defaults to 50.
  • Tags — Optional comma-separated tags. A job must have every listed tag to match. Leave empty to consider jobs with any tags.

Output shape

One output item per matching job in an active poll; no output when there are no new matches. Each item contains the job fields plus reason, reasonCode, and reasonSolution fields when available.

Only terminal jobs are considered. Job IDs are stored in workflow node static data to avoid firing again for recently seen jobs; up to 500 IDs are retained. The first scheduled poll initializes this history without emitting items. In manual mode, the poll returns at most the first matching job.

Links

Discussion