Skip to content
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.

[question] Behaviour when Activity.do_not_complete_on_return() is called #32

Open
MahendiraBoopathi opened this issue Jun 28, 2022 · 1 comment

Comments

@MahendiraBoopathi
Copy link

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.

@MahendiraBoopathi 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
@MahendiraBoopathi
Copy link
Author

update: client.wait_for_close() is a blocking call. starting this call in a separate thread will solve this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant