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.