Troubleshooting Issues

Incorrect/Missing Edlink Mappings Errors

• Issue: User information appears incorrect or does not map properly into Edlink (e.g., grade levels, agent relationships, genders, time zones).
• Potential Resolutions:
  1. In the source sidebar, click Validate Configuration and confirm validation succeeds. This seeds default source→Edlink mappings.
  2. Open Field Mapping for the source and review mappings such as grade levels and agent relationships.
  3. Remap mislabeled values via the dropdowns.
  4. Run a new sync; the updated mappings will be applied.

No Schools Found During Discovery

• Issue: The discovery cron finds zero schools for a Wonde client.
• Potential Resolutions:
  • Confirm the API key is present in external.wonde.wonde_api_key for the client.
  • In Wonde’s portal, ensure at least one school has approved your app.
  • Call GET https://api.wonde.com/v1.0/schools with the key to verify the list is non-empty.
  • If access was recently granted, wait for the next discovery run or trigger it manually.

Core Entity Sync Failed

• Issue: Sync jobs fail with HTTP 401 for multiple/all schools.
• Potential Resolutions:
  • The key may be invalid/expired/rotated. The client must get a new multi-school key from Wonde.
  • Beware the time-gap scenario: discovery succeeded earlier, but the key became invalid before sync. Treat as a client-level credential issue, not a per-school issue.
• Issue: API returns 403 with messages like invalid_permissions or mentions of a missing scope (e.g., contacts.read).
• Potential Resolutions:
  • Verify in the Wonde portal that your app has been granted access by the school(s) and that the relevant data scopes are enabled.
  • Required Scopes:
    • schools.read
    • students.read
    • employees.read
    • contacts.read
    • classes.read
    • courses.read
    • enrollments.read
    • sessions.read
    • periods.read
    • departments.read
  • After scopes are enabled, the next sync will pick up the data automatically.

Contacts Not Linking To Students

• Issue: API returns 403 with messages like invalid_permissions or mentions of a missing scope (e.g., contacts.read).
• Potential Resolutions:
  • Verify in the Wonde portal that your app has been granted access by the school(s) and that the relevant data scopes are enabled.
  • Required Scopes:
    • schools.read
    • students.read
    • employees.read
    • contacts.read
    • classes.read
    • courses.read
    • enrollments.read
    • sessions.read
    • periods.read
    • departments.read
  • After scopes are enabled, the next sync will pick up the data automatically.

Missing UPI Students

• Issue: Student is missing
• Potential Resolutions:
  • Student was not correctly added to Wonde database. They are missing a UPI (identifier)

Missing UPI Employees

• Issue: Employee is missing
• Potential Resolutions:
  • Employee was not correctly added to Wonde database. They are missing a UPI (identifier)

Missing Class ID

• Issue: Class is missing
• Potential Resolutions:
  • Class was not correctly added to Wonde database. It are missing a ID (identifier)