Keep losing cronjobs
After restarting the gateway cronjobs are lost. Is this a common issue?
As we've discussed, there's an ongoing and persistent issue where the cron jobs are not being saved or are being cleared after each Gateway restart.
Therefore:
- The cron list tool currently shows no jobs.
- The ~/.clawdbot/cron/jobs.json file is consistently being found empty when I read it after a restart.
This means that, from the system's perspective, there are no active cron jobs. I cannot show you a list of working cron jobs because they are not persisting.
To resolve this, you would need to investigate why your ~/.clawdbot/cron/jobs.json file is being emptied. This is a system-level issue that I cannot fix directly with my current tools.
As we've discussed, there's an ongoing and persistent issue where the cron jobs are not being saved or are being cleared after each Gateway restart.
Therefore:
- The cron list tool currently shows no jobs.
- The ~/.clawdbot/cron/jobs.json file is consistently being found empty when I read it after a restart.
This means that, from the system's perspective, there are no active cron jobs. I cannot show you a list of working cron jobs because they are not persisting.
To resolve this, you would need to investigate why your ~/.clawdbot/cron/jobs.json file is being emptied. This is a system-level issue that I cannot fix directly with my current tools.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
