You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.
Registered n number of activities which is part of one workflow. Workflow execution is started and activity 1 is called. I donot want activity2 to start until activity 1 completes, so used Activity.do_not_complete_on_return() inside activity implementation code. Later this activity is completed by external services.
But until activity 1 completes the process thread is blocked.
Is there anyway to unblock the thread so that it can process other events ?
and still activity 2 can be dependent on completion of activity 1.
The text was updated successfully, but these errors were encountered:
MahendiraBoopathi
changed the title
[question] Cadence activity blocks the process thread when do_not_complete_on_return() is called
[question] Behaviour when Activity.do_not_complete_on_return() is called
Jun 28, 2022
Registered n number of activities which is part of one workflow. Workflow execution is started and activity 1 is called. I donot want activity2 to start until activity 1 completes, so used Activity.do_not_complete_on_return() inside activity implementation code. Later this activity is completed by external services.
But until activity 1 completes the process thread is blocked.
Is there anyway to unblock the thread so that it can process other events ?
and still activity 2 can be dependent on completion of activity 1.
The text was updated successfully, but these errors were encountered: