Cron trigger doesn't work after a bad configuration was corrected. #186168
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Bug
What GitHub Actions topic or product is this about?
Schedule & Cron Jobs
Discussion Details
Hello, GitHub community!
I'm encountering a problem about workflow cron triggers in my public repository, Greatdori! - Nightly Build.
There's my triggers (full workflow configuration file here):
As you can see in the screenshot below, this workflow isn't triggered with reason "Scheduled" after Jan 27 at 4:20 AM GMT+8. The next 2 runs were failed due to my wrong configuration. I fixed the problem after that, but the cron doesn't trigger my workflow anymore.
Beta Was this translation helpful? Give feedback.
All reactions