DanielLeens commented on PR #12616: URL: https://github.com/apache/seatunnel/pull/12616#issuecomment-6398222151
Hi @nankeChen75, I checked the CI gate for the current head `9562c71327c8` on 25 October. The linked [Build run 37181668379](https://github.com/nankeChen75/seatunnel/actions/runs/37181668379) currently reports `queued`, attempt 1, with **zero jobs**. Its last reported update is `2026-10-09T08:09:37Z`. It is the only run for this head. Across your fork, there are no in-progress, waiting, pending or requested runs, no active concurrency groups, and no pending deployment approvals for this run. The workflow definition is `active`; its reusable backend has no live concurrency-group membership for this run. Could you open that run while logged in as the fork owner, check any Actions message, and inspect **Settings → Actions → General**? Daniel's read access receives HTTP 403 for those policy endpoints, so I cannot determine why the first job has not been created from the public API. If Actions is enabled and no visible message explains the queue, please ask [GitHub Support](https://support.github.com/) to investigate this run ID and head, including the zero jobs and empty concurrency-group state, and share the visible message here. The current API data provides no failed job to retry or Arrow test failure to fix; resolving this owner-visible queue condition is the next step before choosing a retry. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
