Hello Suraj,

I haven't played with this, so this is just speculation, but one thing you could try would be a stepstatusfail check in the transition of the connect wait step. However, that said, the help does say the following (emphasis added)...

Checking the method status

This method updates the pxMethodStatus property. See How to test method results using a transition.

When a {SQLPage:pagename} directive appears as the first line of the SQL code on the Save tab, a top-level page named pagename is created. If errors occur, properties on that page contain additional error details. (When RunInParallel is selected, this page is not available to the original requestor.)

 If it turns out that the stepstatus fails to capture the error because it's on the SQLPage:pagename and your requestor doesn't have access to that page, you may be out of luck. In that case you may need to reconsider your design and come up with another form of parallelism that allows for additional error trapping.

Thanks,

Mike