Added check to control if a dataflow is unscheduled in order to schedule it #279
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
juldrixx
changed the title
mh013370
reviewed
Aug 2, 2023
|
Would a dataflow be unscheduled on first deployment? Can you describe what scenarios this condition presents itself? |
It works the same as before. Only, instead of constantly starting and activating processors and services, we check whether any processors or services are switched off. Any point of caution? |
mh013370
approved these changes
Aug 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's in this PR?
New check to control if a dataflow is unscheduled in order to schedule it.
Why?
To prevent spamming Start and Enable and overflowing of the Flow History Configuration
Checklist