Description:
According to the documentation, businessTransactionID is a unique identifier for tracing purposes across function calls and is optional in the schema. User wants the same businessTransactionID value in all the PlanItemExecuteRequest for same plan.
Symptoms:
Different businessTransactionID in PlanItemExecuteRequest for same plan.
Cause:
The businessTransactionID corresponding to an order is sent in all the outgoing messages such as PlanItemExecuteRequest, PlanItemSuspendRequest, PlanItemExecuteFailedRequest, etc. for that order along with the other attributes such as orderID, orderRef, and planID. Although it is optional in the schema, the process component/external component should return the businessTransactionID from the request message back in the response messages to the Orchestrator.
If the same businessTransactionID is mapped back in the response messages to Orchestrator, it will always be same in further messages from Orchestrator.