Skip to content
Notis

Clear queued workflows that have waited too long

Set a clear waiting-time rule and have Notis cancel matching queued runs during a recurring review.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Cancel a workflow run

Cancels a workflow run in a github repository if it is in a cancellable state (e.g., 'in progress' or 'queued').

Why this helps

Queued runs that no longer matter can obscure current work and leave you unsure which jobs need a closer look.

  • Apply a waiting-time rule that fits your workflow.
  • Review eligible runs on a recurring schedule.
  • Reduce queue clutter without a manual search.

Setup

Build it in a few focused steps.

  • 1Connect Celigo and GitHub once in the Notis portal.
  • 2Create an automation in Automations, then New Automation, and give it a name.
  • 3Describe which queued runs count as old enough to cancel in one instruction.
  • 4Choose a recurring schedule and where run reports should go.
  • 5Test with one real example and confirm the report.

Questions about this workflow

Can the workflow identify how long each run has waited?

It can use run details available to Notis. Specify the waiting-time rule and confirm the relevant details are available when you test.

Will running jobs also be canceled?

Describe queued runs as the target in your instruction. The action can cancel eligible runs, so be explicit about which states you want Notis to consider.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Celigo to GitHub. A trigger fires from one place; an action lands in another.

Celigo triggers

GitHub actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

List repositories starred by the authenticated user

Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.

ActionInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

Add email for auth user

Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.

ActionInstant

Add app access restrictions

Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.

ActionInstant

Add a repository collaborator

Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.

ActionInstant

Add a repository to an app installation

Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.

ActionInstant

Connect any two apps with Notis in the middle.

Celigo and GitHub, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.