Discovery schedules are not triggering as expected when the previous discovery schedule is canceled, despite the "Even if canceled" option being enabled in the schedule configuration. Based on the expected behavior, subsequent discovery schedules should continue to execute regardless of whether the previous schedule completed successfully or was canceled. However, the next scheduled discovery does not start, resulting in missed discovery runs.
