> Source: [sk185019](https://support.checkpoint.com/results/sk/sk185019)

# sk185019 - Gaia Job Scheduler Changes to Migrated Entries from R81.10 or Lower Versions Are Not Saved

| Property | Value |
|----------|-------|
| Solution ID | sk185019 |
| Date Created | 2026-06-02 |
| Last Modified | 2026-11-12 |
| Technical Level | General |
| Products | Security Gateway, Security Management Server |
| Versions | R82.10, R82 |
| OS | Gaia |

## Symptoms

- * After an in-place upgrade, editing an existing Gaia Job Scheduler entry in Gaia Portal shows the message `Save Successful`.

  However, reopening the entry shows the previous command, and the change is not applied.
* The same behavior occurs in the Command Line Interface (CLI). Updating a job and saving the configuration appears to succeed, but the stored command remains unchanged.

  Example:
  ````

  ```````  
  ````
  [Gaia - clish]````  
  ````
  set cron job daily-backup command "/usr/bin/rsync -a /var/log/ /var/backup/"````  
  ````
  save config````  
  ````
  show cron job daily-backup command````  
  ````
  command "/usr/local/bin/old-backup-script.sh"````  
  ````
  ```````  
  ````
  ````
* This issue occurs only for Job Scheduler entries that:

  * Were originally created on R81.10 or earlier
  * Were migrated during an in-place upgrade
* The issue does not occur:

  * On newly installed systems
  * On systems upgraded from later source versions
* Observed workarounds:

  * Delete the affected Job Scheduler entry and recreate it.
  * Create a new Job Scheduler entry with the required command and rename it to the original job name.

## Cause

In newer Gaia versions, the Job Scheduler database includes additional fields (hourly and interval).

Entries migrated from R81.10 or earlier do not include these fields.

When Gaia attempts to update such entries, the update process does not complete, and the system keeps the original configuration. The user interface does not reflect this condition and shows a successful save message.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R82.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82.20/index.html) starting from Take 14
* [Jumbo Hotfix Accumulator for R82.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82.10/Default.htm) starting from Take 52
* [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 132

If you choose not to upgrade, Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.  
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

<br />

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content