[Jan-Hendrik Peters (nyanhp)]

Confluence enacts a rate limit, which can be countered using the values supplied in their response headers on receiving an HTTP 429 error. This PR implements rate-limiting countermeasures by sleeping for the amount of time specified in the Retry-After header.

---

Technical details

Implementation approach: Evaluate HTTP 429, use values supplied by Atlassian, observe ~400 pages get created
Issue-plan progress: ?
Standards alignment: The new code adheres to PowerShell best practices and the code style found in this project
Convergence Sweep: I don't know what that means

Relevant issues (or links)

[Copilot]

🟡 Changes recommended

The near-limit check cannot convert array-valued headers, causing errors even on successful requests.

1 open issue

• Handle X-RateLimit-NearLimit header string arrays correctly · New

What changed in this PR

This PR adds rate-limit handling to the shared Confluence REST helper to reduce throttling and retry requests rejected with HTTP 429.

Changes:

• Adds a 500 ms delay when the near-limit response header is true.
• Waits for the Retry-After interval before retrying a throttled request once.

File	Description
src/​functions/​public/​API/​Invoke-ConfluenceRestMethod.ps1	Adds near-limit delays and HTTP 429 retry handling.

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Consecutive HTTP 429 responses still terminate operations because the retry bypasses further rate-limit handling.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Retry repeated 429 responses using each Retry-After value

src/​functions/​public/​API/​Invoke-ConfluenceRestMethod.ps1:190

If the retry also returns HTTP 429, execution goes straight to the error handler without waiting for that response's Retry-After value. For example, a 429 → 429 → 200 sequence aborts after the second response, so sustained throttling still interrupts bulk page creation. Use a bounded retry loop that reads the updated header on each 429 and throws when the retry budget is exhausted or a non-retryable error occurs.

1 resolved since last review

• Handle X-RateLimit-NearLimit header string arrays correctly

_{Review effort: Balanced}