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

A way to manually progress a failing async call #2295

Open
matt2e opened this issue Aug 8, 2024 · 1 comment
Open

A way to manually progress a failing async call #2295

matt2e opened this issue Aug 8, 2024 · 1 comment

Comments

@matt2e
Copy link
Collaborator

matt2e commented Aug 8, 2024

Prereq: async based features showing up in console

Use cases:

  • I have a async call that has failed a number of times and will retry in a frustratingly long time for now. I have fixed the underlying issue, and i want to trigger the retry now.
  • I have an async call that is failing and it will continue to fail until the full retry policy is expired which will take a frustratingly long time due to the defined policy. I want to mark the call as failed so that the subscription/fsm can progress.
    • Would the catch verb be called in this case?
@github-actions github-actions bot added the triage Issue needs triaging label Aug 8, 2024
@matt2e
Copy link
Collaborator Author

matt2e commented Aug 8, 2024

partner project had a use case for this today where they wanted to try their newly deployed code but were waiting on a previously long retry policy

@ftl-robot ftl-robot mentioned this issue Aug 8, 2024
@deniseli deniseli removed the triage Issue needs triaging label Aug 8, 2024
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