This reference details sync errors that occur when incoming data conflicts with existing Edlio records, configuration limits are violated, or safety thresholds prevent unintended mass changes.
Conflicts with existing data (IDs 301–306)
When incoming records conflict with existing database records, Edlio excludes the incoming row rather than making unsafe assumptions.
Ambiguous Person Association [301]
The incoming record matches more than one existing person in Edlio, typically because Source ID, Employee ID, and Student ID point to different existing profiles.
Resolution: The log lists all matching profiles and their IDs. Search for them under Manage People (check unpublished profiles as well):
Matches from another synced file or role: Records will conflict until source data is corrected; two people cannot share an Employee ID or Student ID with different Source IDs. Correct SIS data.
Matches from a legacy manual import: If the duplicate profile has never signed in, delete it; otherwise, edit the profile to clear conflicting IDs.
Ambiguous Account Association [302]
The incoming record's login identifier matches multiple existing user accounts. Nothing is created, updated, or deleted for this record. Also triggered by collision guards preventing account reassignment when held by an active user.
Resolution: Follow the same resolution as Ambiguous Person Association [301].
Person Source ID Mismatch [303] & Account Source ID Mismatch [304]
An existing profile matches by identity attributes, but carries a different Source ID. Common when a person was previously synced from another source, mapping rules changed, or the SIS re-keyed the user.
Resolution: Locate the existing record in Manage People:
Same role syncing: Clear the existing person's Source ID in the dashboard and rerun the sync.
Different role syncing: Ensure both roles configure the same Source ID column, or notify the district that one person is being sent under two separate identifiers.
District ID Mismatch [305]
The matched account belongs to a user in another Edlio district. When cross-district connect is disabled, this is raised as a Warning and the account is excluded. When cross-district connect is enabled, this is logged as Info (expected behavior).
Resolution: Look up the person in the named other district. If no longer active there, delete the stale record in that district. If legitimately active in both, distinct email addresses are required.
Account Email Mismatch [306]
An account matched by Source ID, but the username/email in the feed differs from Edlio's current record. The account update is skipped.
Resolution: If the SIS address change is legitimate, enable username updates for that role in sync settings to allow automatic updates, or correct the SIS export.
Configuration and limits (IDs 400–406, 500)
Missing Options [400]
The sync ran with no identity options, an SFTP account has no mapped organizations, or a classroom sync has no schema.
Resolution: Verify configuration settings. "No organization is associated with ftp account..." indicates the SFTP account exists but has not been mapped to a school/district entity.
Invalid Person Type [401] & Invalid District [402]
Configured role is not one of student, parent, staff, or community [401], or the district ID resolves to no organizations [402]. These indicate broken configuration or system bugs — escalate to Edlio Engineering.
Invalid Organization [403]
Error: A configured organization ID lies outside the district (app connection, dashboard account, role, or managed org). Resolution: Ensure configured IDs point to valid district sites.
Warning: A single person row maps to no organization. Resolution: Check the row's site identifier against the account's school mapping table.
Large Scale Threshold Reached [404]
Critical safety guard. When tripped, NO changes are made to the database. Tripped under three conditions:
The percentage of records modified/deleted exceeds the safety threshold.
There are zero existing records of that type in the system.
For classrooms: a wholesale replacement resembles two sync feeds overwriting each other (detected by rapid delete/recreate cycles).
Resolution: Always inspect the log counts first (projected inserts, updates, and deletes). If legitimate (e.g., beginning of school year, term rollover, or initial data load), enable Allow large-scale sync on that identity. If classroom deletion thrashing is indicated, disable the competing sync source rather than raising thresholds.
Conflicting Options [500]
Settings that cannot coexist. As an Error: App connection missing role ID during app account creation, dashboard account missing type during account creation, or SFTP schema configuring multiple relationship syncs (unsupported). As a Warning: Unsupported relationship type ignored, or app account creation skipped because login is disabled for the district.
Resolution: Errors halt the run — correct sync settings. Warnings complete the run but indicate omitted features.