Schedule Optimization ML Solution Waiting for TrainingIssue An ML Solution used by Schedule Optimization remained in a "Waiting for Training" state and did not complete within the expected timeframe. Symptoms ML Solution remains in "Waiting for Training" longer than expected.Schedule Optimization processing completes later than intended.Retry activity can occur after the originally expected execution window.Schedule changes may occur after work has already been assigned. Facts Disabling retries is possible by setting the glide.platform_ml.training.retry.limit property to 0.Disabling retries entirely may not be suitable for environments that require retry functionality.No supported configuration exists to allow retries while restricting them to a specific time window.The glide.platform_ml.training_timeout property can be used to define the timeout duration for ML Solution training requests.Review confirmed no ongoing issue with the Schedule Optimization functionality involved in this case. Release Yokohama Resolution Review the glide.platform_ml.training_timeout property if a shorter timeout period is desired.If retry functionality is not required, configure glide.platform_ml.training.retry.limit to 0 to disable retries.If retry functionality must remain enabled, there is currently no supported method to prevent retries from occurring after a specific time of day.No corrective action was required for the platform because the occurrence was determined to be isolated and subsequent training requests completed successfully.