Retry failed ETL syncs instantly when the fix is on your side
Even the most reliable data pipelines can hit a snag; expired credentials, permission changes, schema updates, and so on.
Previously, when a sync or table in Weld failed too many times, it was automatically locked to prevent repeated failed runs. That safety mechanism helps protect your pipelines, but it also meant you had to wait for the lock to clear before retrying.
🔁 Retry failed syncs directly
You can now clear certain user-resolvable locks and retry a failed sync directly from the Weld UI after you’ve fixed the issue.
This gives you more control and faster recovery, especially when you’ve already solved the root cause. Locks that are not user-resolvable will continue to prevent retries to keep your data safe.
Common use cases
- You’ve fixed an issue in a custom connector or cloud function and want to re-run the sync
- You updated expired API credentials or fixed a permission error
- An external service is back online after an outage
⚙️ How it works
- Go to the connection or table with the failed sync
- If the lock is user-resolvable, you’ll see a Retry option
- Click Retry sync to trigger it immediately
- Weld will re-run the job with your latest setup
No need to wait for a manual unlock, just fix and retry.
Faster recovery, smoother pipelines
This update makes Weld’s sync management more flexible and developer-friendly. Data engineers can now recover from transient issues faster, test fixes in real time, and keep data pipelines running smoothly, while still maintaining the safety of non-user-resolvable locks.
A small change that saves time and keeps your data moving.
