Bug Report: Socket closed, when running workflow

[trey-rosius]

Describe the bug

Workflow times out and never fully runs.

== APP - loan-broker == raise _InactiveRpcError(state) # pytype: disable=not-instantiable == APP - loan-broker == grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: == APP - loan-broker == status = StatusCode.UNAVAILABLE == APP - loan-broker == details = "Socket closed" == APP - loan-broker == debug_error_string = "UNKNOWN:Error received from peer {created_time:"2024-08-27T12:01:05.756489+01:00", grpc_status:14, grpc_message:"Socket closed"}" == APP - loan-broker == > == APP - loan-broker == == APP - loan-broker == During handling of the above exception, another exception occurred: == APP - loan-broker ==

To Reproduce Here's the Complete Code https://github.com/trey-rosius/loan_broker_application

Run the code and start a workflow with this endpoint http://localhost:5006/v1.0/seek-loan Expected behavior I expected the workflow to run and execute it's individual activities.

Screenshots

Additional context

[famarting]

Hi, we have been investigating the issue and although we haven't reproduced this exact error we already found various errors that could led to this bug

We will apply our bug fixes as soon as possible.

Btw I connected to your project, connected the app and created a workflow which is now in failed state.

And sorry for the inconvenience!

[famarting]

I think I have identified the root cause of the bug. We currently have a bug that makes us not being able to support workflows executing activities concurrently. i.e https://github.com/trey-rosius/loan_broker_application/blob/main/loan-broker/workflow.py#L40 . We are actively working on getting a bugfix.

One option that could unblock you could be to rewrite that workflow so it executes the different activities in sequence instead of using the yield when_all statement

[trey-rosius]

I think I have identified the root cause of the bug. We currently have a bug that makes us not being able to support workflows executing activities concurrently. i.e https://github.com/trey-rosius/loan_broker_application/blob/main/loan-broker/workflow.py#L40 . We are actively working on getting a bugfix.

One option that could unblock you could be to rewrite that workflow so it executes the different activities in sequence instead of using the yield when_all statement

Thanks for the feedback. However, the main objective of this workflow was to execute the tasks in parallel and then aggregate the results. The Fan In / Fan Out Pattern. I have a another workflow that executes tasks sequentially. I'll test it out and see if it works

[famarting]

@trey-rosius hey! yesterday we deployed the fixes to prod, would you be able to double check if the issue is fixed for you? Thank you

[trey-rosius]

@famarting It works like a charm.

Thanks. I'll close this issue now