Problem

Pressing the "Update Hermes" button in the dashboard completely wipes all scheduled cron jobs. This has happened multiple times. Every time an update is applied, all cron job configurations are destroyed.

What Should Happen

Cron jobs should be stored in a database or config file that persists across updates. The update process should NEVER touch user data — only Hermes core code should be updated.

What Actually Happens

1. User clicks "Update Hermes" in the dashboard
2. All scheduled cron jobs are deleted
3. Every cron job configuration (schedule, prompt, name, settings) is gone
4. User has to manually recreate all cron jobs from scratch

Impact

• All scheduled tasks stop running — monitoring, scanning, and automation all halt
• This is a recurring bug that has happened multiple times
• User loses hours of work reconstructing cron job configurations
• Production automation is disrupted

Root Cause

Likely one of the following:

1. Cron job storage is in the same location as code that gets overwritten during updates
2. The update process runs a migration that clears the cron table
3. Cron data is stored in a file that gets deleted/replaced during update
4. No backup of cron data is made before update runs

Expected Behavior

• Cron job data MUST be preserved across updates
• If database migrations are run, they should be additive only (never delete user data)
• There should be a backup of user data before any update

User Context

This has happened multiple times. The same issue keeps occurring despite being reported before. The update process is destructive to user data and this is unacceptable for any software, let alone an agent framework running production workloads.

Complaint

The Hermes team continues to release code that destroys user data. Dangerous code is being shipped without addressing known issues. Cron jobs are a critical part of automation workflows and should NEVER be deleted by an update. This needs to be fixed permanently, not just patched over each time it happens.