-
Notifications
You must be signed in to change notification settings - Fork 3
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
No Start State #914
No Start State #914
Conversation
I should probably standardize the capitalization. For example, when I query the workflow I get
and when I start and then query I get
So I need to make it NO START |
I would think the Workflow state would be Not Started and the tasks could be blank. |
I can do that instead! |
@Leahh02 This looks good to me and works well. You will need to fix the conflicts. I've asked @kabir-vats to review it, if he has time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice addition to allow a user to specify a workflow and verify the tasks and a first step in verifying the workflow dependencies.
This should allow the user to cancel a workflow submitted with the no-start state. The correct state should also come up when they query the workflow. The correct state should also appear in the graph database.