Async LRO poll timeout (450s) too low for large API imports; abandons still-running operations

[Alexey-Zheltov]

Command that triggered the bug

apiops publish

Expected behavior

For large API specifications, apiops publish should wait long enough for APIM's asynchronous import (LRO) to complete. APIM continues processing the import server-side; the CLI should not give up while the operation is still succeeding.

Actual behavior

The CLI aborts polling after a hardcoded 7.5-minute deadline and reports the API as failed, even though the APIM operation is still running and eventually succeeds:

ERROR NOOP api/: Async operation polling timed out after 450s for apis/
ERROR NOOP api/: Async operation polling timed out after 450s for apis/

This reproduces with large specs (observed with files in the ~340 KB–670 KB / 10k–20k line range), whose import takes more than 7.5 minutes.

apiops CLI version

1.0.0

Environment details

Windows self-hosted agent; Node v24.15.0 / npm 11.12.1; Windows PowerShell 5.1; APIM SKU Developer.

CI/CD environment

Azure DevOps

Is this bug blocking you?

Yes

[github-actions]

🏷️ Triage Recommendation

Type: type:bug
Effort: effort:S — the fix is likely a configurable timeout parameter or a bumped default constant; the LRO polling loop already exists.
Domain: src/ — async LRO polling logic in the publish command (APIM REST client / operation poller)
Confidence: high (88%)
Uncertainty: none — clear bug report with concrete reproduction steps, error message, and file-size range. Effort could rise to M if the timeout needs to become user-configurable (CLI flag + validation) rather than just a constant increase.

Reasoning

The CLI has a hardcoded 450 s (7.5 min) polling deadline for APIM async import (LRO) operations. Large API specs (~340 KB–670 KB) can take longer, so the CLI abandons still-running operations and reports failure. This is a confirmed bug with a clear root cause.

Recommended next steps

• Locate the 450 s constant in the LRO polling code and either raise it or make it configurable via a --lro-timeout CLI option.
• Consider reading an environment variable (APIOPS_LRO_TIMEOUT_SECONDS) as a lightweight escape hatch before adding a full CLI flag.
• Verify whether the APIM SDK / @azure/arm-apimanagement poller exposes a timeout option that can be threaded through.
• Add a test or note in docs about large-spec publish behavior.

Generated by Contract test: verify context separation for #251 · 16 AIC · ⌖ 8.5 AIC · ⊞ 6.5K · ◷