Job Chain Call ignores Scheduling Parameter Start Time once after upgrade to 9.2.10 or 9.2.11

Issue

After the upgrade from a version below 9.2.10 to a version higher than 9.2.10, you can run into an upgrade issue.

All Jobs in a Scheduled State during the upgrade that have the Scheduling Parameter Start Time set on a Call will be affected.
If multiple Calls are using the Scheduling Parameter to delay the execution of a Call, all will ignore the Scheduling Parameter.
When multiple Chains are scheduled (due to Pre Submit Count or multiple Schedules), all chains are affected.

Issue: The Scheduling Parameter is ignored, and the Call will not wait for the indicated start time; it will run as soon as the Step starts (no delay).

Any Jobs manually or automatically (re)scheduled after the upgrade are no longer affected.
This even stands when an affected job is rescheduled; the next occurrence will be correct.

Scheduling Parameter location in the Job Chain Editor:

Reporting

Two Reports have been created to attempt to show the affected Jobs.

• Show the Jobs that already experienced the issue.
• Show the Jobs that are expected to experience the issue at their Runtime.

Import the attached Car-file to use these Report files.

Note: Both Reports will be in the Application named Upgrade_SchedulingParameter_Reports

Applies to:

 RMJ/RMF 9.2.10 - 9.2.11.0

Resolution:

After Upgrade

You can use the Reports to identify affected jobs. Reschedule the ones listed with the status Scheduled to prevent those Jobs from running into the issue.

Before Upgrade

The Development Team will implement a fix in a future version to prevent this issue from occurring after the upgrade. The Start Time Scheduling Parameter will not be ignored after an upgrade.

Ticket Reference:

RCORE-43278