This article covers common errors and data quality issues that can occur with the Wonde integration, along with their causes and resolutions. It is intended for d6 support staff troubleshooting sync problems for Wonde-integrated schools.
Mission Control > Customer Success > Integrations > Wonde > Sync Settings
"A sync is already in progress": Another sync is running for this community. Wait for it to complete (typically 2 to 10 minutes). If it runs for an unusually long time, escalate to the technical team.
"Sync ignored: Integration sync is paused": The sync has been manually paused. Unpause it via the Sync Settings page.
"Failed to fetch data from Wonde API": This can be caused by network issues, API downtime, rate limiting, or an expired token. Escalate to the technical team to check connectivity, verify the API token, and consult the Wonde status page. The system sends a failure email to support with details.
"Name is required": The assignment set was saved without a name. Enter a descriptive name.
"At least one group is required": No d6 Portal groups were selected. Select one or more groups to populate.
"At least one group or class is required": No Wonde groups or classes were selected. Add at least one group or class assignment.
"Invalid filter expression": There is a syntax error in the filter expression. Use the "Validate" button to check. Common mistakes include misspelled field names, using = instead of ==, missing quotes around text values, and using fields not available for the selected person type.
This is the most common data quality issue. Check the following in order:
Parental responsibility flag: The parent contact must have "parental responsibility" set to true in Wonde. This is the most frequent cause. Ask the school to verify and update this in their MIS.
Student filter: Parents are only included if their child passes the student filter. If the student is filtered out, the parent will not appear either.
Parent filter too restrictive: For example, has_email == true will exclude parents who only have a phone number. Review the filter using the preview tool.
No contact information: A member record can be created without email or phone, but they cannot receive communications.
Assignment set not saved: Verify the assignment set exists and has the correct groups selected.
Data-only sync was run: A data-only sync skips Phase 2, which is the phase that updates groups. Run a full sync instead.
Filter expressions returning no results: Preview the filter expressions to confirm they match at least some members.
Parent-child dependency: For parents to be included, their children must pass the student filter first. Check both filters.
The parent must have "parental responsibility" set to true in Wonde. At least one assignment set must include students or parents for the sync to establish relationships. Verify that both parent and child passed their respective filter expressions. Relationship sync runs during Phase 2, so ensure a full sync has been completed.
Small schools (under 500 students) typically take 1 to 3 minutes, medium schools 3 to 7 minutes, and large schools 7 to 15 minutes. If a sync runs significantly longer than expected, escalate to the technical team.
First confirm when the last sync ran — check the sync history in Mission Control. If the last sync was before the MIS change, run a manual full sync. If the sync ran after the change but data is still stale, the issue may be on the Wonde side — ask the school to check their Wonde Dashboard.
No. Wonde-synced members cannot be manually edited in d6 — any changes will be overwritten on the next sync. The school must update the data in their MIS system, and the correction will flow through on the next sync.
Complex filter expressions evaluated against large datasets can slow down the preview. Try using more specific filters or previewing individual groups instead of all at once. The sync itself is not affected by preview speed. If it consistently takes more than 30 seconds, escalate to the technical team.
Last updated: April 2026 | Version 1.0