Matching push is recorded, but no Actions workflow or run appears

[hapektas-jpg]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Workflow Configuration

Discussion Details

A private repository receives a push to a branch explicitly included in its workflow’s push filter, but no Actions run appears.

The workflow exists at the exact pushed commit under .github/workflows/. Its trigger configuration includes push for the default branch and the relevant feature branch, plus an unfiltered pull_request trigger.

Verified:

• Literal on: key; no YAML boolean-key conversion.
• Official actionlint 1.7.12 exits 0 without diagnostics.
• No path filters, job conditions, or commit skip directives.
• Normal Git push using user OAuth authentication, not GITHUB_TOKEN.
• Actions enabled; same-repository PRs are mergeable.
• GitHub records the matching push event.
• Workflow/run list APIs return HTTP 200 with zero results.
• Workflow lookup by filename returns 404; PR check lists are empty.
• No workflow approval request or explanatory error is visible.

Local lint success is not being treated as GitHub acceptance. The underlying cause remains unknown.

What supported diagnostic or escalation route can identify why this recorded push creates no run, including a possible account/repository restriction or undisclosed server-side rejection?

Private identifiers, source code and raw logs are intentionally omitted.

[4Raisan]

Your checks already rule out several common trigger mistakes. The workflow-file 404 is a useful part of the evidence, but it does not by itself prove an account restriction or reveal why the event was rejected.

The supported escalation route is GitHub Support: https://support.github.com/. In a private ticket, include the repository URL, pushed commit SHA, branch, UTC push time, and the x-github-request-id response headers from the workflow-list and filename-lookup requests. Ask Support to investigate workflow discovery/event processing for that specific push and confirm whether any repository or account restriction applies. Keep authentication headers, tokens and private source out of the ticket attachments.

If feasible, a small, manually dispatched workflow on the default branch can help distinguish “Actions cannot discover any workflow” from “this particular push never schedules one”; it is a diagnostic comparison, not a guaranteed repair. There is no supported public API that exposes every internal rejection reason.

Disclosure: drafted with OpenAI GPT-6.