Flux fails to handle multiple reconciliation commands in a row

[cpressland]

Our organisation unfortunately uses Octopus Deploy to package up applications and ship OCI Artifacts to our container registry. Octopus then updates the Flux Git Repo with new OCIRepository and Kustomization resources, once complete, it executes the following commands on the destination cluster:

$ flux reconcile source git flux-system
$ flux reconcile source oci <app_name>
$ flux reconcile kustomization <app_name>

This requirement came from developers wanting immediate feedback from within the Octopus Web UI for if shipped artifacts are deploying etc.

Unfortunately we hit a limitation where the OCIRepository resource isn't available immediately after issuing the $ flux reconcile source git flux-system command, leading to issues like this:

Wed, Mar 5th 2025 13:24:32 +00:00  Info          Reconciling git source ...
Wed, Mar 5th 2025 13:24:32 +00:00  Error         ► annotating GitRepository flux-system in flux-system namespace
Wed, Mar 5th 2025 13:24:32 +00:00  Error         ✔ GitRepository annotated
Wed, Mar 5th 2025 13:24:32 +00:00  Error         ◎ waiting for GitRepository reconciliation
Wed, Mar 5th 2025 13:24:32 +00:00  Error         ✔ fetched revision flux@sha1:e60d24d10d8749d234722b1f0702eb357fd54622
Wed, Mar 5th 2025 13:24:37 +00:00  Info          Reconciling OCI source ...
Wed, Mar 5th 2025 13:24:37 +00:00  Error         ✗ ocirepositories.source.toolkit.fluxcd.io "containerisation-poc-api" not found

Any suggestions for how we can best mitigate around this? It does appear each flux reconcile command is blocking, but as the follow up command can fail this doesn't appear to be 100% accurate. Would forcing a reconciliation of the flux-system kustomization between these steps help?

[matheuscscp]

Change flux reconcile source git flux-system to flux reconcile kustomization flux-system --with-source