Execute action after concurrency cancellation #40550
Replies: 2 comments
-
Hi there @caronicolas and welcome to our community! Thank you for asking a great question 🙂 To get started, introduce yourself in our official introduction thread |
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.
-
Select Topic Area
Question
Body
We used the concurrency in our workflow to cancel it if a new workflow in the same concurrency group started.
It works well, but we have two issues:
- Another GitHub action in another repo calls our workflow. When the cancellation occurs, the principal repository (i.e., the one who launched the workflow) keeps the action in pending status. We want to see a fail instead of pending because if two developers launch the same workflow, the first one only knows the cancellation after checking in the other repos what his workflow's status is.(solved)I can give more details if I need to be more precise.
Thanks for your help!
Beta Was this translation helpful? Give feedback.
All reactions