Flaky test: Test_ACI cleanup — APPLICATIONS.CORE/GATEWAYS|DELETE exceeds 1200s timeout on aci-app delete

[willdavsmith]

Summary

The corerp-cloud scheduled functional test suite is intermittently failing during cleanup of Test_ACI. When the test driver calls rad application delete --yes -a aci-app, the backend APPLICATIONS.CORE/GATEWAYS|DELETE async operation does not complete within the 1200s server-side timeout, so the CLI command returns non-zero and the whole scheduled run is marked failed (even though the actual test assertions had passed).

This was observed at least twice in the 05/25/26 – 06/01/26 on-call window:

• Run 26692916523 (2026-05-30 19:30 UTC) — auto-issue #12023
• Run 26685117482 (2026-05-30 13:32 UTC) — auto-issue #12022

Error signature

✖  test/functional-portable/corerp/cloud/resources (~46m)
    cli.go:752: [rad]     "message": "Operation (APPLICATIONS.CORE/GATEWAYS|DELETE) has timed out because it was processing longer than 1200 s.",
        Error:      Received unexpected error:
                    command 'rad application delete --yes -a aci-app' had non-zero exit code: exit status 1
##[error]Process completed with exit code 2.

Affected workflow

.github/workflows/functional-test-cloud.yaml — Run corerp-cloud functional tests job.

Likely areas to investigate

• Why APPLICATIONS.CORE/GATEWAYS|DELETE for the aci-app gateway is taking longer than 20 minutes (ACI container group teardown? Stuck async op? Polling backoff?).
• Whether this is genuine slowness in the controller, an ACI-side delay, or a stuck reconcile loop.
• Whether the test should skip / be more tolerant of cleanup failures vs. fixing the underlying delete path.

Related

• Auto-generated per-run issues (will be closed as duplicates of this tracker):
  • Scheduled functional test failed - Run ID: 26692916523 #12023
  • Scheduled functional test failed - Run ID: 26685117482 #12022
• Test_ACI was previously unskipped in Unskip Test_ACI test #11708.