Hi @tpettersen ,
The retry handling would work potentially in Forge resolvers. We would likely use such a solution.
However there is also rate limiting for Forge macro PDF exports, and during PDF export macros can get rate limited, even if a macro does not use a resolver because PDF export also runs e.g. Custom UI code.
I think the rate-limiting should be looked at holistically. Atlassian chosen a distributed cloud architecture, and the rate-limiting needs to adopt to this. For example the rate-limits for frontend calls should be different than the rate limits for batch backend calls (which can be throttled easily). I think sorting this out is worthy of a separate RFC (and not touched upon in 2026 point-based rate limits )