Action Responses not persisted in ForgeState when two parallel actions complete their execution at the same time intermittently

We are noticing an intermittent issue where we have two actions within the same node and whenever the two actions finish their execution at the exact same time, the action response is not getting persisted in the forge state and our schema failures at GetOutput with exception System.NullReferenceException:Object reference not set to an instance of an object

Upon retry the issue goes away..

Here is the first attempt where it failed.

2024-05-20 10:01:08.5802526 The Action response for action : ********* is {"StatusCode":1,"Status":"True","Output":""}
2024-05-20 10:01:08.5802528 The Action response for action : ******** is {"StatusCode":1,"Status":"True","Output":""}

Next attempt where it passed

2024-05-20 10:01:58.3472478 The Action response for action : ***** is {"StatusCode":1,"Status":"True","Output":""}
2024-05-20 10:01:58.4162777 The Action response for action : ***** is {"StatusCode":1,"Status":"True","Output":""}

Start by reproducing the case with two actions in one node completing simultaneously, then trace how their responses are persisted in ForgeState before GetOutput. Done means both action responses remain available in ForgeState and the schema no longer fails with a NullReferenceException; add regression coverage if the existing test structure is found.