Re. TM suspend/continue, in the continue function we create a faked_env (similar to that used in failure route handling). The problem here is that any async route block we execute will be classified as a FAILURE ROUTE block regardless of where we are in message processing process. This will cause problems for many cfg commands that are restricted to REQUEST_ROUTE only. Was this the intention and if so, why? 

Cheers

Jason