More resilient imports, clearer report coverage
Recover from temporary import interruptions while keeping completed report data intact.
By AppCradle · Published
Large reports and temporary service interruptions should not make every import feel like a fresh start. This archive edition brings together the import and report-coverage improvements available by September 18.
Improved
Continue from completed work
App Store marketing imports save completed reporting dates as they progress. Recoverable interruptions can continue from those checkpoints, preserving completed data instead of repeating the entire job.
Temporary failures are retried within bounded limits. When a run cannot continue, its visible status still matters: a failure is not silently presented as a fully completed import.
Better handling of large reports
The reporting pipeline handles larger Apple report inputs and breaks database work into manageable batches. The goal is to finish complete reporting slices without replacing valid data with an unfinished result.
Fixed
More accurate coverage signals
Apple lifecycle-report selection and Google Play vitals retrieval received improvements. Empty results remain distinct from observed zero activity. A quality report without observations does not prove an app had no crashes or ANRs.
Using these improvements
Check Imports and the report coverage messages when a metric is unavailable. An older interrupted run may need Retry all to resume. Provider reports that have not yet been published still depend on the provider’s next available data.
See the bigger picture.
Bring your store reports together and spend more time understanding what they mean.
Try for free