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.

Sign up for GitHub

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

Jump to bottom

Problem: user async completion is not always available #57

Open
sevein opened this issue Feb 6, 2020 · 0 comments
Open

Problem: user async completion is not always available #57

sevein opened this issue Feb 6, 2020 · 0 comments
Labels
Severity: low An inconvenient situation where the software is usable but could be better.

Comments

@sevein
Copy link
Member

sevein commented Feb 6, 2020

We introduced async completion in v0.22.0 but the same solution is expected to be available in other areas of the workflow. One goal is to stop abusing the workflow retry which is discouraged in Cadence unless it's necessary in operational contexts. Workflows should almost never stop.
@sevein sevein modified the milestone: Backlog Jun 10, 2020
@sevein sevein added the Severity: low An inconvenient situation where the software is usable but could be better. label Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Severity: low An inconvenient situation where the software is usable but could be better.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sevein