Skip to main content

Troubleshooting — Schedules

Instance Does Not Start/Stop at the Configured Time​

Symptom: The Instance does not change state at the Start time or Stop time configured in the schedule.

Cause: The system allows a maximum delay of 15 minutes from the scheduled time. This is expected behavior.

Resolution:

  1. Wait up to 15 more minutes past the configured time.
  2. If the Instance still has not changed state after 15 minutes, check the Status column of the schedule — ensure the schedule is in Active status.
  3. Check the Instance status in the Instances attached table on the schedule detail page, and see whether the most recent execution result is Failed.

Execution Result Shows Failed​

Symptom: In the Instances attached table, the Latest start or Latest stop column shows Failed.

Common causes:

  • The Instance is in an error state (Error) that prevents it from being started or stopped.
  • The Instance has been deleted from the system but has not been removed from the schedule.
  • A temporary system error occurred at the time of execution.

Resolution:

  1. Check the Instance status in Compute Engine → Instances.
  2. If the Instance is in an error state, resolve the Instance issue first.
  3. If the Instance has been deleted, remove it from the schedule.
  4. If it was a temporary error, the system will retry on the next scheduled execution.

Cannot Find an Edit Button to Modify the Schedule​

Symptom: You want to change the time or frequency of a schedule but cannot find an edit option.

Cause: Instance schedules do not support editing after creation — this is a system design limitation.

Resolution:

  1. Note the current configuration of the schedule you want to change.
  2. Delete the current schedule (click Delete on the detail page).
  3. Create a new schedule with the desired configuration as described in guide-create.md.
  4. Reattach the Instances to the new schedule.

Schedule Shows Expired Status But End Date Has Not Yet Passed​

Symptom: The schedule status is Expired even though the End date you configured is still in the future.

Possible cause: The schedule's timezone differs from the timezone displayed in your browser, causing the actual End date to have already passed when calculated in UTC.

Resolution:

  1. Open the schedule detail page and check the Timezone and End date fields.
  2. Convert the End date to the configured timezone to confirm the actual value.
  3. If you need to extend it, delete the schedule and create a new one with a new End date.

Schedules Menu Is Not Visible in the Navigation Bar​

Symptom: The left navigation bar does not have a Schedules item under Compute Engine.

Cause: You are viewing a context where the current Project is not linked to any VPC, or you have not selected the correct Project/VPC.

Resolution:

  1. Check that you have selected the correct Project and VPC at the top of the page.
  2. Schedules are available on both General VPC and Specific VPC — if it is still not visible, contact support.