Network Management

NCM job keeps disabling because Ending On date is in the past

When an NCM job keeps disabling itself, the usual cause is that its Ending On date is already in the past, so the scheduler treats the job as expired and automatically reverts it to Disabled right after you enable it. Extending the Ending On field to a future date (or effectively removing the end date, depending on version) allows the job to stay enabled and run on its schedule.

First published date

2/10/2026 10:24 PM

Last published date

2/10/2026 10:24 PM

Overview

  • An NCM job is manually enabled, but:

    • The job immediately shows as Disabled again, or

    • The job does not run at the expected time and appears disabled on the Jobs page.

  • No recent changes were made to credentials, nodes, or job type.

  • When you edit the job and review the schedule, the Ending On field shows a date in the past.

Product section

Network Performance Monitor

Cause

NCM jobs use a schedule that includes a Starting On and Ending On date (internally stored as StartingOn and EndingOn in the job schedule).

If the Ending On date is in the past, the scheduler treats the job as expired:

  • The job will not run after the Ending On date.

  • When you attempt to re‑enable the job, it is immediately set back to Disabled because the schedule is still considered expired.

This often occurs when:

  • The job was created with a fixed end date that has now passed.

  • The job was imported or cloned from another environment where the Ending On date was already near expiration.

  • Older NCM versions used default Ending On values that were later improved in newer releases to avoid this behavior.

Resolution

Update the job schedule so that Ending On is set to a future date (or removed, if you want the job to run indefinitely).

Step 1: Open the affected job

  1. In the SolarWinds Web Console, go to:
    My Dashboards > Network Configuration > Jobs.

  2. Locate the affected job in the list.

  3. Click Edit for that job.

Step 2: Check the job schedule

  1. In the job wizard, go to the schedule step:

    • For Basic schedules, this is usually the page where you set frequency (Daily, Weekly, etc.) and the start time.

    • For Advanced schedules (CRON), review the same page where the CRON expression is configured.

  2. Locate the Ending On field.

  3. Confirm that the date is set to a past date (for example, last year or an earlier month).

Step 3: Correct the Ending On date

  1. Change Ending On to a future date that meets the customer’s retention or change‑management policy.

    • For ongoing jobs (for example, nightly backups), choose a date several years in the future.

  2. (If available in your version) you may clear any explicit end date so the job runs indefinitely, depending on UI options.

Step 4: Save and re‑enable the job

  1. Click Next through the wizard and then Save the job.

  2. Back on the Jobs page, make sure the job now shows as Enabled.

  3. Optionally:

    • Run the job Now to confirm it starts and completes successfully.

    • Verify that the next Scheduled Time is shown correctly on the Jobs list.