Skip to main content
If your CRM integration experiences a temporary outage — whether due to an expired API key, a CRM provider issue, or a WeGive maintenance window — you may notice that gifts appear in your CRM in a batch after the outage resolves, sometimes with gift dates from several days earlier. This is expected behavior and means your data is catching up. Here’s how it works.

​
No gifts are lost during an outage

WeGive records every donation the moment it happens, regardless of whether the CRM sync is working at that moment. Gifts are stored in WeGive first, then pushed to your CRM. If the connection is temporarily down, those gifts simply wait until the sync resumes.

​
How the catch-up works

WeGive runs a nightly batch sync for each CRM integration (Virtuous, Planning Center, Raiser’s Edge, and others). Every night, this process does two things:
  1. Syncs yesterday’s gifts — all donations from the previous day that haven’t been sent to your CRM yet.
  2. Sweeps for any older gifts that were missed — this catch-up pass looks for donations from any date that still haven’t made it to your CRM.
This means that after an outage resolves, the very next nightly sync will automatically pick up everything that was missed — not just one day’s worth, but the entire backlog. You don’t need to do anything manually.

​
Why gift dates may look different from the import date

When the catch-up sends missed gifts to your CRM, each gift keeps its original gift date — the date the donor actually gave. The import batch itself is stamped with today’s date (you may see it labeled something like “WeGive Import 10/18/2026”), but the individual gift records inside that batch carry their real dates. For example, if your integration was down from Monday through Wednesday and reconnects Wednesday night:
  • Thursday morning’s batch will include gifts from Monday, Tuesday, and Wednesday
  • Each gift will show its original gift date (Monday, Tuesday, or Wednesday respectively)
  • The import batch name will show Thursday’s date
This is by design — it ensures your CRM reporting reflects when donors actually gave, not when the sync happened to run.

​
What you’ll see in Integration Logs

After an outage resolves, you’ll likely see two log entries from the catch-up run:
  • A Batch entry for the previous day’s gifts (the normal nightly sync)
  • A Batch Missing entry for any older gifts that were caught up
Both should show a status of Processed if everything synced successfully. If you see Ignored, that means there were no missed gifts to catch up — which is normal if the outage was very brief. For more on reading Integration Logs, see Understanding Integration Logs.

​
What to do after an outage

In most cases, nothing. The catch-up is fully automatic. However, you may want to:
  1. Check your Integration Logs the morning after the outage resolves. Look for a Batch Missing entry with status Processed — that confirms the catch-up ran and your data is current.
  2. Spot-check a few records in your CRM to confirm they arrived with the correct gift dates and amounts.
  3. If you see errors, open the log’s Details view for the specific error message. Common causes include CRM-side validation rules that reject records — these need to be resolved in your CRM before the gift can sync.

​
Frequently asked questions

How long does the catch-up take? The catch-up runs as part of the regular nightly batch, which is scheduled to start at the same time every day. Most catch-up batches complete within minutes, even for large backlogs. Will I get duplicate gifts in my CRM? No. WeGive tracks which gifts have already been synced by recording the CRM-side ID on each transaction. A gift that has already been successfully pushed will never be pushed again. What if the outage lasted more than a few days? The catch-up sweep has no time limit — it checks for un-synced gifts from any date, not just the last few days. Even a week-long outage will be fully caught up on the first successful nightly run after the connection is restored. Do I need to manually trigger a resync? No. The catch-up is automatic. Manual resync (available on individual records and table views) is only needed if a specific record was blocked by a CRM-side issue, such as a validation rule.
Last modified on October 20, 2026