Issue Summary:

Some Connect to Forge migrations are not being upgraded reliably due to a rate limiting issue caused by a component of the migration eligibility calculation logic.

As per the changelog entry CHANGE-2540, the first update from Connect to Forge automatically rolls out to customers when an app is eligible, over a 120 hour (5 day) period.

Due to a rate limiting issue, some installations are failing to complete this rollout within the expected window.

Expected Results

All eligible Connect app installations are progressively migrated to the Forge version within the 120-hour rollout period as per the documented behaviour.

Actual Results

Some Connect to Forge migrations fail or are skipped intermittently. The root cause is a rate limiting issue triggered during the migration eligibility calculation logic. The issue cannot be reliably replicated.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.