The Orchestration cannot promote the properties to message context by default like pipelines can do by using the msg.Context.Promote() method. Inside Orchestration one has to create a correlation set and initialize that correlation set while publishing the message. Then the BizTalk Engine will promote the property to the message context.
List the persistent Points
The procedure of saving your running orchestration states ate certain point is called persistence. Orchestration Engine persist a running instance which is based on the design of orchestration. There are few events or stages which triggers the persistence operation called persistence points.
Following is the list of persistent points:
Orchestration instance is suspended or finished
System shutdowns in a controlled manner
Engine determines it want to dehydrate
Atomic or long running transnational scope ends
At debugging breakpoints
Execution of other orchestrations through the start orchestration shape
At the send shape.
When the Orchestration Engine is shut down; through the controlled shutdown of the host or abnormal circumstances. The engine tries to persist but if that fails, the Orchestration instance will resume from the last successful persistence point.
