DanielLeens commented on PR #12931: URL: https://github.com/apache/seatunnel/pull/12931#issuecomment-6337292577
Thanks for the clear update, @Nikk8091. I checked the current head: [Build](https://github.com/apache/seatunnel/runs/118842639245) still reports `action_required` with **Workflow run detection failed**; it has not run the tests. Your reported dispatch HTTP 422 is stronger evidence of an activation problem than the workflow's `active` flag. Daniel cannot read your repository's Actions permissions endpoint (HTTP 403), so I cannot independently confirm the account-level reason. Please check the Actions tab and any activation/restriction banner as the fork owner, resolve that gate, then manually start **Build** on this PR's branch. If dispatch still returns the same 422 after activation, please take that response and its request ID to GitHub Support; changing the connector code or repeatedly pushing commits will not resolve a rejected workflow dispatch. The current branch is behind `dev`, which I recorded, but I have no evidence that syncing would fix this activation gate. There is no new code review in this reply: the head is unchanged and my previous source-level conclusion stands. Thanks for keeping the scope focused and distinguishing your local results from the required head-specific CI run. Keeping the draft until that run passes makes sense. -- 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]
