Hello CurtisDo,
Thank you for your question.
What you’ve described is a known limitation of ZAPTEST which our R&D team already aware of and we hope a new fix will be published soon.
Meantime the only workaround to this issue is as follow:
1. Record a very small and insignificant test without any special events (As always follow the recording wizard);
2. Stop the test and make sure the application you wish to test is already opened;
3. Start your recording session now (You’ll notice you are recording the already opened application).
4. In ZAPTEST before executing the test make sure all its initialization details are being noted as expected).
Please contact ZAP for further help.
Thanks,
Sasha