Changing Time-Based Schedules to Cycle-Based
Last updated: November 18, 2026
Cycle-based schedules can appear to launch early or immediately show as past due when the schedule history or machine counter does not align with the new setup.
Why this happens
This commonly happens when a schedule that was previously time-based is changed to cycle-based. L2L can still have prior schedule history, while the cycle-based schedule now evaluates against the machine's current cycle count. If that current count has already passed the launch threshold, the PM can launch right away and show as past due.
Recommended approach
L2L does not recommend changing an existing schedule's interval type from time-based to cycle-based.
Instead:
Verify the machine's true cycle count from your source of record, such as your PLC, MES, SCADA system, or another validated counter.
Update the machine cycle count in L2L so it matches that source.
Create a new cycle-based schedule rather than converting the old time-based schedule.
Inactivate the old schedule if it is no longer needed.
If you want to reuse the original schedule name, rename the old schedule first so the new schedule can use that name.
Important behavior to know
Cycle-based PMs launch when the machine's cycle count crosses the Launch X cycles prior threshold.
If the machine's cycle count in L2L is ahead of where you expected, the PM may launch immediately or appear thousands of cycles past due.
Changing a machine's cycle count affects all cycle-based schedules tied to that machine, not just one PM.
Time-based schedules on that machine are not affected by changes to the machine cycle count.
How to avoid repeat issues
When moving from time-based scheduling to cycle-based scheduling, treat the new cycle-based schedule as a fresh setup. Confirm the machine counter first, then create the new schedule with the correct launch and due values.
If you need to review multiple schedules, export the schedule data and compare the current machine cycle count with each schedule's history before making changes.