-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhanced Scheduling with Conditional Task Execution in Pterodactyl #5033
Comments
Duplicate of #4160 |
No, not really, It's not only about conditional but mainly about absolute planning that it's respected whenever the main server is started after or before the planned task.
|
To be able to shedule force wipe (on rust server) with special commands we need too be able to use 0 19 * * 4 [ "$(date +%m --date '7 days ago')" != "$(date +%m)" ] && This job has a condition that checks if the month of the date 7 days ago is different from the current month, which will be true only on the first Thursday of the month. Also same if it is a normal thursday. this is the only thing stopping me from doing more automations and make my life easier! |
This requires the server to be on. |
Is there an existing feature request for this?
Describe the feature you would like to see.
Pterodactyl features a scheduling system resembling cron tasks, which operates based on real-time triggered events or intervals.
One drawback is the system's inability to initiate scheduled tasks if the host server starts after the specified time, limiting its effectiveness in certain scenarios.
For example, this limitation could lead to missed task executions when the host server reboots beyond the scheduled timeframe. Like a server startup.
Describe the solution you'd like.
A new feature could be added to Pterodactyl to enable conditional scheduling, allowing users to set specific criteria for task execution.
This would enhance planning capabilities by providing more flexibility and intelligence in automation workflows.
Additional context to this request.
No response
The text was updated successfully, but these errors were encountered: