Let's go over some of the out-of-the-box options for executing a pipeline from inside your orchestration. It struck my mind first that the MSMQT adapter IS in fact the messagebox. MSMQT Set up a schedule with 1 MSMQT send port and 1 MSMQT receive port sharing the same MSMQT queue name (for example ' loopback' would make a lot of sense) Create a correlation type and set based on the my MSMQT label property. Assign the MSMQT message-label to a newly created GUID inside your orchestration. Try to do...