Your Wild Apricot pull is stuck, paused, or rate-limited
Your Wild Apricot data or file pull looks slower than expected, shows Paused — retrying, or won’t respond to Pause or Resume.
What’s happening
Section titled “What’s happening”Wild Apricot limits how many requests it accepts per minute, so a large pull naturally takes time — MapleGather shows an estimate up front and slows down automatically rather than failing when it hits that limit. A few specific situations look like the pull is “stuck” but aren’t:
- A group is waiting on another group. Events, registrations, invoices, and payments all link back to contacts, so those groups wait for Contacts to finish first — this shows as Waiting, not an error.
- A transient rate-limit pause. MapleGather automatically resumes from exactly where it left off — you won’t lose progress or get duplicate records.
- Wild Apricot is temporarily unreachable. A brief outage on Wild Apricot’s side during the pull — MapleGather keeps retrying automatically, so you don’t need to do anything.
- Pause or Resume didn’t take effect (WebDAV file pulls only). A WebDAV pull can briefly be in a state where it can’t be paused or resumed yet (for example, mid-way through writing a large file) — this clears itself within moments. An API pull has no manual pause — it only shows Paused — retrying on its own and resumes automatically.
- Your Wild Apricot credentials changed mid-pull. The pull stops safely at the last file or record it completed, rather than continuing with a credential that no longer works.
How to fix it
Section titled “How to fix it”- Check the connection status at the top of the pull screen — if it says needs attention, see Your Wild Apricot connection was rejected or needs reconnecting, then come back to resume.
- If a group shows Waiting, confirm Contacts is included in this pull, or has already finished — dependent groups won’t start until it has.
- If you’re running a WebDAV file pull and Pause or Resume didn’t respond, wait a few seconds and try again — it’s a brief timing issue, not a failure. (An API pull can’t be paused manually — it pauses and resumes itself.)
- For a large pull, you can safely close the tab and check back later — it keeps running, and progress also shows in the Bulk Operations panel.
- If a group has an orphaned record (for example, a registration that references a contact that wasn’t pulled), pull Contacts first, or skip that row when you review the import.
If that didn’t work
Section titled “If that didn’t work”If a WebDAV file pull shows The file pull failed and it doesn’t resolve after reconnecting, select Retry on that message — this resumes from where the pull left off rather than starting over. An API pull has no Retry button: if it stops making progress, reconnect when the screen shows This connection needs attention, then start the pull again. You can also bring the same data across without a pull: export it from Wild Apricot as a CSV file and import it — see Upload and map your import file.