Scheduled actions in an enterprise #124392
Replies: 1 comment
-
🕒 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're working on setting up our repositories in GitHub, moving from Azure DevOps. We are planning on implementing some nightly workflows across our repositories. We're expecting that when we're done to be in the order of 1-2 thousand. According to the docs when the user that last sets the cron schedule leaves the org the workflow will no longer be scheduled. How do organizations handle scheduled workflows at scale. If it was just a handful, no big deal, but we're talking 1 to 2 thousand with some having multiple workflows being scheduled, having someone go in and re-enable workflows or update workflows just isn't a viable option. Along with that note, if the person that set the cron job leaves the org, the workflow gets disabled, who gets the notification that it was disabled?
Beta Was this translation helpful? Give feedback.
All reactions