It appears we were ignoring the $InstanceId param in Start-DurableOrchestrationExternal. This is not happening in the worker, so we probably introduced that bug early on (not sure why) and forgot to revert it.
In the "BasicExternalOrchestrator" test, we have added multiple activity invocations around the external event. These are writing to the output buffer, which changes the result of the orchestration. I believe this is consistent with the current SDK's behavior. Therefore, the fix is to either save the output of the invokeActivities to variables (so they get captured before they enter the output buffer) or to not have those activity invocations at all. I went for the latter approach, but I'm ok with either.
~Update: seems the external event test is failing still (though the instanceID test is passing). Debugging that right now~
This PR should address 2/3 of the failing E2E tests in https://github.com/Azure/azure-functions-durable-powershell-private/pull/39.
It includes 2 fixes:
~Update: seems the external event test is failing still (though the instanceID test is passing). Debugging that right now~