This problem analyzer helps you deploy changes to flow definitions.
What triggers this problem analyzer?
If you're using version 44 (Winter '19) of the metadata API to compare and deploy your metadata AND you include any flow definitions, we'll warn you.
What problem is this analyzer solving?
One reason to stop using them is that flow version numbers aren't carried across between environments, so there's no guarantee version 2 of the flow in the source organization is the same as version 2 in the target organization! This also means that your source flow definition can specify an active version which isn't present in the target.
If you try to deploy a flow definition which references an invalid version number as the active version, your deployment will fail.
How does it work?
We'll show you a warning. This will then let you decide whether to deploy the flow definitions or whether to remove them from your deployment.