Refresh an advertising report
Refresh updates campaign statuses and metrics.
How to use it
- Check the selected game, account and range.
- Select Refresh beside the section or group heading.
- Wait for the refresh to finish. If a next-attempt time is shown, use that as your guide.
Advice and practical context
Refresh is observation
Refresh retrieves available current statuses and aggregates. It cannot recreate missing history or guarantee identical freshness for every field. A Roblox limit can provide the next allowed attempt time.
Keep the last known truth
After a partial error, successful campaigns remain updated while failed ones need targeted review. Do not discard valid history or retry before the displayed wait. Refresh time is not necessarily the exact campaign start or stop time.
Use campaign-level timestamps, not only the global indicator, when comparing state before and after refresh. If the key is cooling down, wait until the displayed time; repeated requests do not make data fresher and can prolong the operational issue.
Technical detailsCalculations, permissions and behavior
Ads API cooldown
Background Ads refreshes only a due range: short ranges at most every 15 minutes, 30 days hourly, 6 months every 6 hours, and one year or all time daily. A Roblox 429 is not retried repeatedly inside one refresh. MARPLA keeps the complete Retry-After, never truncates a long pause, and does not let a manual click or generic failure shorten an already scheduled interval.
The last confirmed report stays visible until a successful response.
Shared cooldown for one Ads key
A Roblox Ads cooldown applies to the connected key across every game, browser tab and MARPLA server process. Requests using one key pass one at a time through a shared gate, so parallel tabs cannot create a request burst; a different key continues independently. After a 429 or another failed response with Retry-After, no further Ads request using that key is sent before Roblox's exact time, and a shorter late response cannot reduce the stored cooldown.
Creating and closing group tests uses the same protection. MARPLA does not automatically retry campaign-changing operations after an ambiguous network or server failure, preventing duplicate changes.
Campaign continuity during partial responses
The main table always keeps standalone campaigns and creative test groups together. Roblox Ads' experimental list may temporarily omit an existing campaign or return a row without a Universe ID. MARPLA does not delete a stored campaign in that case: it collects known Campaign IDs from groups, exact creative relations, recent reports and hidden-row state.
Those stored campaigns and their last campaign-level figures are reconstructed as soon as the page opens, even while a fresh Roblox sync is temporarily unavailable. During the next successful update, MARPLA refreshes their official status and campaign-level report directly by Campaign ID.