Argo verification issues

[jsbroks]

With error

{
  "ok": false,
  "body": "{\"error\":\"permission denied\",\"code\":7,\"message\":\"permission denied\"}",
  "json": {
    "code": 7,
    "error": "permission denied",
    "message": "permission denied"
  },
  "headers": {
    "Date": [
      "Tue, 21 Apr 2026 17:08:08 GMT"
    ],
    "Vary": [
      "Accept-Encoding"
    ],
    "Content-Type": [
      "application/json"
    ]
  },
  "duration": 577,
  "statusCode": 403
}

Clicking redeploy fixes the issue, but then it's stuck showing a verifying badge (I think unrelated).

Seems to only happen when adding new resources to a deployment (in this case, I added a new environment to a deployment)

• potentially trying to verify before the application exists? So it gets a denied error?
• Or it might not be using the correct credentials on first deploy

[jsbroks]

Idk if related, but documenting it

failed to upsert application: All attempts fail: #1: rpc error: code = InvalidArgument desc = application spec for ctrlc-sync-agent-<redated>"is invalid: InvalidSpecError: Unable to generate manifests in components/ctrlc-sync-agent: rpc error: code = Unknown desc = error building helm chart dependencies: failed to login to registry https://<redated>"/helm/charts/: failed to login to registry: failed to get command args to log: `helm registry login https://<redated>" --username ****** --password ******` failed exit status 1: WARNING: Using --password ****** the CLI is insecure. Use --password-stdin. Error: authenticating to "<redated>": not found

This also showed, for some but not others, redeploying fixed the issue as well

[jsbroks]

Update: when I tried redeploy, it almost got resolved, but some still showed permission denied. Clicking redeploy directly on them fixed the issue. I wonder if there is a rate-limiting issue? Not sure

[adityachoudhari26]

#1021
closed this PR that makes the default check more lenient, will close this one if we stop noticing this issue after we deploy