Checks completed automation does not trigger for private org repo; Run History stays empty

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

A GitHub automation with a Checks completed trigger does not fire at all for a private organization repository.

The automation is active, the repository is selected, and the trigger is configured as:

  • Checks completed
  • On Any Completion
  • On PRs
  • by Me

After pushing a new commit to an open PR, GitHub Actions completed successfully, but the automation never started. The automation Run History remains empty: 0 successful runs and 0 failed runs.

This looks similar to the previously reported organization-repo webhook/auth silent drop issue, but it is still happening for a Checks completed trigger.

Steps to Reproduce

  1. Create an automation for a private organization repository.
  2. Configure the trigger as Checks completed / On Any Completion / On PRs / by Me.
  3. Push a new commit to an open PR authored by the same GitHub user.
  4. Wait for GitHub Actions and Cursor Bugbot checks to complete successfully.
  5. Open the automation Run History.

Actual result: no run is created and Run History stays empty.

Expected Behavior

When a matching PR check completes, the automation should create a run, or at least record a failed/skipped run with a reason.

Operating System

MacOS

Version Information

Cursor dashboard / cloud automations. I am using the current Cursor web dashboard and Cursor desktop app; I can provide exact version details privately if needed.

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A. No automation run was created, so I do not have a run ID/request ID.

Additional Information

Evidence from the affected private org repo PR:

  • The PR is open and not a draft.
  • The selected repository matches the automation trigger.
  • The PR author, workflow run actor, and triggering actor are the same GitHub user selected by by Me.
  • GitHub Actions check runs completed with success.
  • Cursor Bugbot also completed with success.
  • The automation Run History still shows No Runs Yet.

One additional detail: the head commit also has several third-party GitHub App check suites stuck in queued state even though the actual GitHub Actions jobs are completed. I am not sure whether the automation is being dropped because of org-repo webhook authorization, or whether the Checks completed trigger is waiting on stale queued check suites.

This may be related to the org repo webhook/auth issue discussed here:

The May 29 update says GitHub webhook handling was improved, but this looks like either a regression or a case not covered by that fix.

The repository, PR URL, branch name, and commit SHA are private. I can share them privately with Cursor staff if needed.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. This looks like a known limitation of the “by Me” filter on the “Checks completed” trigger.

Right now, for check_suite events, this trigger matches the “by Me” filter against the actor who reported the check result, which is often a CI bot like github-actions[bot], not the PR author. Because of that, “by Me” doesn’t match and the run gets silently skipped, so Run History stays empty. That lines up with what you’re seeing.

Workaround: switch the trigger filter from “by Me” to “by Anyone”. If needed, you can add extra filtering inside the automation. Let me know if that works.

Also, you’re on an individual account without a team. For private org repos, webhook authorization for personal installations sometimes isn’t allowed. It’s the same area discussed here: Automations not triggering for organization repositories (works for personal repos). If you can connect the org repo through a team account, that’s more reliable.

The “by Me” filter issue is a known bug and I’ve reported it internally. I can’t share an ETA for a fix yet, but I’ll post here if I get an update. About third-party check suites stuck in “queued”: since no run is created at all, the main cause is most likely the filter, not waiting for checks. But if after switching to “by Anyone” you see the trigger waiting on stuck suites, tell me and we’ll dig into that separately.

7

I’m also getting this issue even if it’s set to “by Anyone” – tried opening MR with cursor or by myself

  • note: this is a personal repo

image
image1662×552 29 KB

image
image1790×1128 226 KB

image
image1864×1234 294 KB

8

Hey, thanks for the screenshots. Your case is a bit different from the original one in this thread. You have the filter set to “by Anyone” and it’s a personal repo, so the “by Me” bug is unlikely to be the cause here.

One thing that stands out is that both PRs (#273 and #283) are in Draft status. In most cases, automations don’t run on draft PRs, only on non-draft ones that are ready for review. Try clicking “Ready for review”, wait for the checks to finish, and then see if a run gets created.

If the trigger is still silent on a non-draft PR, please start a new thread with the details repo, PR link, automation config, and a Run History screenshot so it doesn’t get mixed up with the original issue. Then we can look at it separately.