We are also affected by this issue and would strongly support prioritizing this enhancement.

When a GitOpsSync selector, whether applicationRegex, applicationsList, or applicationLabels, matches zero applications, the step reports Success even though no application was refreshed or synced. This creates a silent deployment failure: a typo, stale service/environment name, incorrect label, or outdated selector can result in a pipeline appearing successful while deploying nothing.

As a workaround, we currently need an additional ShellScript step to inspect <+stepGroup.steps.<step>.gitops.applications> and fail the pipeline when the list is empty.