---
title: Persistent schedules
description: By default, scheduling information is persistent. The schedule state is stored in the repository rather than in memory. This ensures that schedules survive server restarts and effectively manages execution across a cluster. In a persistent model, a scheduled task launches on only one node in the cluster.
component: pingoneaic
page_id: pingoneaic:idm-schedules:persistent-schedules
canonical_url: https://docs.pingidentity.com/pingoneaic/idm-schedules/persistent-schedules.html
---

# Persistent schedules

|   |                                                                                                                          |
| - | ------------------------------------------------------------------------------------------------------------------------ |
|   | You can [schedule jobs](../identities/manage-scheduled-jobs.html) directly in the Advanced Identity Cloud admin console. |

By default, scheduling information is persistent. The schedule state is stored in the repository rather than in memory. This ensures that schedules survive server restarts and effectively manages execution across a cluster. In a persistent model, a scheduled task launches on only one node in the cluster.

|   |                                                                                                                                                                                    |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Non-persisted (in memory) schedules are [deprecated](../product-information/deprecation-notices.html#deprecation-non-persisted-schedules) and will be removed in a future release. |

If the server is down when a scheduled task was set to occur, one or more runs of that schedule might be missed. To specify what action should be taken if schedules are missed, set the [`misfirePolicy`](configure-schedules.html#misfire-policy) in the schedule configuration file. The [`misfirePolicy`](configure-schedules.html#misfire-policy) determines what IDM should do if scheduled tasks are missed. Possible values are as follows:

* `fireAndProceed`

  The first run of a missed schedule is immediately implemented when the server is back online. Subsequent runs are discarded. After this, the normal schedule is resumed.

* `doNothing`

  All missed schedules are discarded and the normal schedule is resumed when the server is back online.