Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Workflows -- use case #509

Closed
dturton opened this issue Apr 28, 2021 · 0 comments
Closed

Workflows -- use case #509

dturton opened this issue Apr 28, 2021 · 0 comments

Comments

@dturton
Copy link

dturton commented Apr 28, 2021

I know this may not be the ideal place to ask for help on this but I thought I would give it a try. Example use case, e-commerce order processing. I saw the new feature for Flow but I am not sure if it solves my use case. My ideal scenario is first an initial job is created then based on its return value then you decide what the next step should be. For example, the order is placed, if the order is above $100 then do these additional jobs and pass the return value to them. I would like to use the Flow feature but I can't find a solution on how to use the return value of a job to decide which task to perform or not to perform next. The reason I need it decoupled as some of the tasks require calling a third-party API, if it fails I want to retry just that one step. I hope it makes sense.

@manast manast closed this as completed Apr 28, 2021
@taskforcesh taskforcesh locked and limited conversation to collaborators Apr 28, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants