How to get the startup_failure reason of a workflow using the API? #57536
Replies: 2 comments
-
|
I have the same need. In the meanwhile I'm scrapping the workflow run webpage. This works nicely for public workflows, with the caveat that it can break at any time the html structure changes. # xargs is only used for trimming
ANNOTATION=$(curl "https://github.com/$GHUSER/$GHREPO/actions/runs/$RUN_ID" 2>/dev/null | grep 'annotation-message.annotationContainer' -A 1 | tail -n 1 | xargs)
ANNOTATION=${ANNOTATION##<div>}
ANNOTATION=${ANNOTATION%%</div>} |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Some workflow runs might not be able to start due to a specific error.
For instance, a workflow which tries to execute a GitHub Action which is not allowed to run for an organization will receive the following error which can be seen in the UI:
My question, is how can I see this same error using the API?
I only manage to get the workflow run (as I have the ID), and I see the conclusion of
startup_failurebut I couldn't find a way to view the full error message like the UI shows.Thanks
Beta Was this translation helpful? Give feedback.
All reactions