Now i am trying to test out using the tctl workflow reset commands on the LongRunningWorflow but when i do i get errors stating non-determinism and that the child workflow (ProxyWorkflow) that i am trying to communicate with is closed so it cant send the external signal anymore.
Workflow reset starts a new workflow execution (with sameworkflow id and new run id) and history is replayed up to the reset event.
By default when parent workflow completes, children do as well. If you want ProxyWorkflow to stay alive after its parent completes
set ParentClosePolicy to ABANDON and start it async, see this post for details.
Is there a reason why ProxyWorkflow is a child workflow?