How to recover from a failed GitRepository deployment (i.e. reconcile stuck at context deadline exceeded)

[RoFz]

Hello,

This is a newbie question. Apologies for that.

I've just deployed the podinfo GitRepository while having a reference not supported by the API on this resource's manifest. It seems like a simple and (probably) common issue that flux should have been able to avoid/prevent/workaround.
It happens though that flux's own Kustomization now is in a failed state (READY = False).
The reconcile command ends after a few minutes with the error context deadline exceeded.

Flux versions:

flux: v2.2.3
distribution: flux-v2.2.3
helm-controller: v0.37.4
kustomize-controller: v1.2.2
notification-controller: v1.2.4
source-controller: v1.2.4

Here's the output of flux get all -A:

NAMESPACE       NAME                            REVISION                SUSPENDED       READY   MESSAGE                                           
flux-system     gitrepository/flux-system       main@sha1:dfaf162d      False           True    stored artifact for revision 'main@sha1:dfaf162d'

NAMESPACE       NAME                            REVISION                SUSPENDED       READY   MESSAGE                                                                                                                                                                                                           
flux-system     kustomization/flux-system       main@sha1:25039e4b      False           False   GitRepository/flux-system/podinfo dry-run failed: failed to create typed patch object (flux-system/podinfo; source.toolkit.fluxcd.io/v1, Kind=GitRepository): .spec.targetNamespace: field not declared in schema

I have already fixed the source manifest and committed the changes. But could not find a way to put flux back on track. I went ahead and removed via flux CLI the bad GitRepository source.

Any ideas?