Scheduled actions in an enterprise #124392
Unanswered
edwardcookemacu
asked this question in
Actions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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