Thanks for the bug report, we’ve found the issue and it’ll be fixed. The problem was that it was checking the architecture of the .exe at the local path rather than the remote mirror path.
For now you can work around this by also having the .exe on the target at a path that matches the local path. For example, if the local path of the .exe is C:\temp\app.exe, have it at that same path on the target. Note that it will still be launched from the mirror path. Sorry for the issues.