---
sourceDocument: Australia Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/service-management-for-the-enterprise

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Service Management

ft:clusterId :

    - sm4e

bundleId :

    - sm4e

workflow :

    - Technology


---

# Changes to maintenance schedules

# Changes to maintenance schedules {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

If you make and save changes to an existing maintenance schedule, any previously
associated records are updated accordingly.  
The following examples explain the types of behavior you can expect after making changes:

* If you change a schedule from a duration-based to a meter-based schedule, the next run time is cleared and the associated records are populated with a next run value instead.
* If the Every field is changed on a meter-based schedule, the next run value is updated based on the existing Last Run Value, or from the current value of the asset if no last run value exists.
* If you change the Field value for a meter-based schedule, the records associated with the schedule have their next run values recalculated based on the new Field value.
* For Interval-based schedules, changing from one Trigger type to another updates the next run time based on the existing Last Run Time value, or from Now if no last run time exists.
{#c_ChangesToMaintSched__ul_v3t_vgw_mr}