Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Orchestrator that does not call any activities will fail #112

Closed
davidmrdavid opened this issue Apr 16, 2020 · 4 comments
Closed

Orchestrator that does not call any activities will fail #112

davidmrdavid opened this issue Apr 16, 2020 · 4 comments
Assignees

Comments

@davidmrdavid
Copy link
Collaborator

Orchestrations are assumed to call an activity at least once, this means that an empty orchestration will throw an exception.

@davidmrdavid davidmrdavid self-assigned this Apr 16, 2020
@priyaananthasankar
Copy link
Collaborator

You mean the orchestrator has to have atleast one call_activity method call?

@davidmrdavid
Copy link
Collaborator Author

Yes, otherwise it throws an exception...at least on my end 🤔

@davidmrdavid
Copy link
Collaborator Author

I think this has to do with how the generator code is structure. There's a do-while structure to it, expecting a task to be scheduled at least once. I think it's a small refactor

@davidmrdavid
Copy link
Collaborator Author

Addressed in: #121

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

No branches or pull requests

2 participants