Orchestrator Gateway Behavior

When AOPD submits a plan to an instance that is unregistered, the Orchestrator acts as a gateway until the instance completes registration with the Broker service.

In this situation, the orchestrator stores the order content in the database. It then sends the plan item execute request to the southbound system, omitting the originator header. Consequently, the instance ID for the order is set to null.

For time-bound orders, where the plan has time-dependency, the time_scheduler table does not have an instance ID.

The system expects the southbound system to respond without altering the original headers. The plan item Execute Reply does not contain the originator header in this scenario.

The Broker service monitors for southbound replies that are missing an originator header. On detection, it assigns an instance to the order and updates the instance ID in both the order and time_scheduler tables.