I am sure I posted this issue a year or so back, but can't find it, so here goes...

We have a process where we receive PDF files, and need to convert the pages to images.  So WF (V12.0.2503.2695) sends it off to DCC (V11.0.2102.97). The steps are sequential, so when DCC is finished it calls the next workflow. The problem is that DCC switches the server name and the repo name, to see need to toggle these through our own tokens.  It's not the worst thing in the world, but annoying each time we have to remember to do that.  Here's the process, server and repo name redacted except for .locals. Initial entry in the first WF Rule:

DCC called via “Schedule PDF Page Generation”

With the option to invoke a workflow on success:

So far so good. Except the invoked workflow has the server and repository values reversed.  This is largely redacted but notice the repo with a .locals domain:

Which leads to all kinds of havoc. Note again the repo identified as Domain.locals.

If I remember correctly this was a known issue a while ago.  Does anyone know where it might be on the punch list?