Limits on Babylon.js AssetsManager retry attempts and duplicate write prevention

The goal is to confirm whether Babylon.js AssetsManager’s built‑in retry mechanism guarantees that an asset’s onSuccess callback is invoked exactly once when developers supplement the default retries with custom calls to task.retry().

Constraints arise because the internal retry counter is not exposed in versions before 5.0, and the interaction between the manager’s maxRetries limit and manual task.retry() calls is not fully documented, leaving uncertainty about whether the state reset could cause the success handler to fire more than once.

Does calling task.retry() after the internal retry counter reaches the maxRetries limit still prevent duplicate onSuccess invocations? If maxRetries is changed during loading, how does the manager reconcile the existing counter? Are there conditions under which onSuccess could execute more than once despite the internal state checks?