1. Proposed title of this feature request
Timing out failing sync and retrying with newer commits in OpenShift GitOps

2. What is the nature and description of the request?
If there is a problem with the deployment and OpenShift GitOps keeps waiting for resources forever (for example because of a misconfigruation), OpenShift GitOps is stuck in syncing status. Even if pushing a new version, OpenShift GitOps stays busy with syncing the previous version. The goal should be to prevent such a condition from happening by eventually timing out the sync after a defined period of time and with a flag to try a newer version (if available) when the sync has failed.

The comment in https://github.com/argoproj/argo-cd/issues/11494#issuecomment-2038591508 documents and summarizes the requirement well and to a level that should help understand what customers are aiming for.

3. Why does the customer need this? (List the business requirements here)
While using OpenShift GitOps, its desired that no manual task/activity should be done to prevent any kind of customization that eventually would need to be reconciled or could even impact running workloads. With the current state of OpenShift GitOps this though is not possible as manual interaction is required when a sync is failing, because the sync needs to be stopped and forced towards a newer commit in git. So to allow true gitops approach, the above requirement needs to be implement/made available as only that way a hands-off approach is possible/doable.

4. List any affected packages or components.
OpenShift GitOps