Hi,

We are encoutering a strange issue with Start Orchestration shape. Staring Orch "ProcessRequest" from "ServiceM" takes 10 mins to trigger it..??

Any idea on what could be the cause ?

If this delay is for all the orchestrations running in your environment, then it could be due to health of your server as whole, then try to identify the bottlenext by running

Messagebox viewer tool and see are there any issues have been highlighted in its report.

http://blogs.technet.com/b/jpierauc/archive/2007/12/18/msgboxviewer.aspx

Also ensure you see the performance monitors..

Also try to identify the pattern for the delay.

If this has occurred for just one time, then I would ignore the issue as one-off.

It has happened three times , every other day and that too happens for just one process, at a particular time window. However we could not see any major trafic around that or other processes getting affected during that window. 

"happened three times , every other day and that too happens for just one process, at a particular time window" - This sounds more like not a server/infrastructure issue. So there is no use in running any health check tools like Messagebox viewer or performance monitor. But give a try with Messagebox viewer to undiscover any thing.

And it sounds the issue is more specific to the process you have implemented. Sometimes if the child/triggered orchestration relies on any other external system and if the external system takes more time to consume the message given by your child orchestration, you could see this type of behavior. But as said it more specific to how you have implement the parent & child Orchestration and not to do with BizTalk or your server's health.