Load Plan Execution Lifecycle

1. Provide Execution Parameters
• When running or scheduling a Load Plan, you must provide specific parameters such as:
• Variable values.
• Contexts.
• Logical agents used for the execution.
2. Create a Load Plan Instance
• Executing a Load Plan creates a Load Plan Instance.
• This instance is distinct from the original Load Plan and serves as a unique execution object.
3. First Load Plan Run
• The first execution attempt of the Load Plan Instance results in the creation of the first Load Plan Run.
• Each execution attempt of the Load Plan Instance is considered a separate run, recorded in the log.
4. Subsequent Load Plan Runs
• If a Load Plan Run is restarted, it creates a new Load Plan Run under the same Load Plan Instance.
• Each attempt to execute the Load Plan is tracked as a distinct run in the system log.
5. Concurrency of Load Plan Instances
• While a Load Plan Instance can only have one active run at any given time, multiple instances of the same Load Plan can be executed concurrently.
• The ability to run multiple instances depends on the Concurrent Execution Control settings for the Load Plan.
6. Concurrency Control
• Concurrent execution of multiple Load Plan instances can be configured based on the load plan's internal ID and the execution settings.
• These settings determine how many instances of the Load Plan can run simultaneously.
7. Tracking Load Plan Runs
• Each Load Plan Run is recorded, and its status (whether successful, failed, or restarted) is preserved in the logs for reference.
• This helps track the execution history of each Load Plan instance.