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

(Re)scheduled batch periodic scenario reported as not running #1902

Closed

jedrz opened this issue Jul 9, 2021 · 0 comments · Fixed by #1913

Labels

bug

Contributor

jedrz commented Jul 9, 2021

To reproduce the issue:

Scheduled scenario is deployed by the batch periodic engine, but the job fails during execution and is reported as FAILED on Flink afterwards.
NK correctly reports it as not running.
User decides to cancel and deploy scenario. Scenario should be scheduled but NK still reports the scenario as not running because the old, failed job is still visible on Flink console.

jedrz added the bug label

jedrz mentioned this issue

Process should be scheduled if previous, failed job is still accessible via Flink API #1913

Merged

jedrz closed this as completed in #1913

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment