We confirmed this problem, it escaped our QA. We plan to release an update with a fix next week. By the way, the same issue happens when macros are started from the command line.
The best short-term workaround is to downgrade to an earlier version.
We confirmed this problem, it escaped our QA. We plan to release an update with a fix next week. By the way, the same issue happens when macros are started from the command line.
The best short-term workaround is to downgrade to an earlier version.