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
More readme updates. #300
base: main
Are you sure you want to change the base?
More readme updates. #300
Conversation
README.md
Outdated
@@ -278,7 +274,7 @@ iWF allows you to start a workflow with a fixed cron schedule like below | |||
// or timed out, the workflow will be retried based on the retry policy. While the workflow is retrying, it won't | |||
// schedule its next run. If the next schedule is due while the workflow is running (or retrying), then it will skip | |||
that | |||
// schedule. Cron workflow will not stop until it is terminated or cancelled (by returning cadence.CanceledError). | |||
// schedule. Cron workflow will not stop until it is terminated or canceled (by returning cadence.CanceledError). |
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.
cadence.CanceledError seems incorrect here given the two backends.
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.
Ahh right. I think we can just remove this part. Returning cancel error is not supported in IWF. The only way to cancel a workflow is call the stop workflow api ( the stopType is cancel by default)
I'll resolve the conflicts shortly. |
Btw there is only one conflict. There is a resolve conflict button in this PR and you can use it to resolve it easily |
More updates to the readme file. Work in process.