Key points
- Pack size is not file capacity.
- Review duplicates first.
- Keep stable batch identifiers.
Detailed explanation
Split larger databases into traceable batches. Follow provider progress and rechecks instead of uploading the same batch again while waiting.
Example
300,000 credits can fund several files, not one 300,000-row upload.
How RefreshList handles it
Workspace and bearer-key API jobs share provider-readiness checks and credit rules.
Limitations
Timing depends on receiving systems and provider availability; there is no fixed completion guarantee.
Related topics
Methodology and sources
Product behavior is described from the current RefreshList implementation and provider contract. Protocol context should be checked against the applicable standards and provider documentation. This page does not create a benchmark or certification.
