Dealing with failed data transfers can be frustrating, but now you don’t have to start over when something goes wrong. There are helpful ways to retry failed pushes efficiently and keep your information accurate.
📌 Why This Matters
When transferring data or syncing information, failures can happen due to connection issues or other interruptions. Being able to retry these pushes without recreating everything saves time, reduces errors, and keeps your workflow smooth. It also keeps your history organized, so you can see what happened and when.
✨ What’s New
- Retry Failed Pushes from History: You can now try again directly from the page where you view past push attempts.
- Batch Retry for Multiple Accounts: If you manage multiple sub-accounts, retry all failed ones with a single click instead of handling them one-by-one.
- Select Specific Accounts to Retry: Choose which sub-accounts to retry instead of always retrying everything, giving you more control.
- Live Progress Tracking: Watch your retries happen in real-time on the same page, so you always know what’s going on.
⏱️ Important Constraints
To ensure your data stays accurate, here are a couple of important limits to keep in mind:
- 48-Hour Retry Window: You can only retry pushes that happened within the last 48 hours.
- Snapshot Version Lock: If the data snapshot has been updated since your original push, retries are disabled and you’ll need to initiate a new push to get the latest information.
🛠️ How to Use It
- Step 1: Head to your data or sync dashboard and open the push history page.
- Step 2: Find the failed pushes you want to retry, then choose to retry individually or select multiple sub-accounts for batch retry.
- Step 3: Watch the progress live to make sure everything completes successfully.
💡 Pro Tip
Regularly checking and retrying failed pushes quickly helps keep your business data consistent, saving you time and avoiding costly errors down the line.
