Skip to main content

Sync Error Reference: Record Identity & Field Validation

Reference catalog for sync errors concerning record identity (IDs 100-104) and field validation warnings (IDs 201-209), including causes and resolutions.

This reference covers sync errors concerning record identity (how records are uniquely identified) and field validations (checks on row values). Understanding these codes helps district administrators pinpoint source data issues and adjust schema mappings.

Record identity errors (IDs 100–104)

Identity identifiers determine how an incoming row maps to an individual in Edlio.

General Error [100]

An unexpected or unclassified failure (e.g., top-level catch, target-list update failure, failed account/person deletion, or an FTP account with no mapped organization).

Resolution: Not for district resolution. Inspect the technical message and escalate to Edlio Engineering if unexplained.

Missing Source ID [101]

A record has no unique identifier from the source SIS. For person records, this halts the sync unless Skip Records with missing Source Id is enabled, which downgrades the error to a warning and skips the row.

Resolution: Check if a better identifier column exists that is guaranteed unique and present on all rows. Natural keys like email fail when blank in SIS. If blank IDs are unavoidable, enable Skip Records with missing Source Id in identity settings.

Duplicated Source ID [102]

Two or more non-identical records share the same Source ID, creating ambiguity. All conflicting rows are skipped. Note: Rows differing only in aggregated fields (grade level, site ID, relationship ID) represent the same person and are not considered duplicates.

Resolution: Confirm the correct column is mapped as Source ID. If the mapping is correct, the district SIS team must resolve duplicate IDs in the source system.

Duplicated Employee ID [103]

Employee IDs must be unique within a district; two incoming records claim the same value.

Resolution: Verify column mapping. If valid, the district must correct duplicate employee IDs in their SIS/HR data. As an immediate workaround to unblock syncing, Employee ID mapping can be temporarily removed and restored once fixed.

Duplicated Student ID [104]

Two incoming student records claim the same Student ID.

Resolution: Confirm column mapping. If mapping is correct, duplicate student IDs must be corrected in the district SIS. Student ID mapping can be temporarily disabled if necessary to complete the run.

Record field validation warnings (IDs 201–209)

Field validation issues are raised as Warnings: the offending field is cleared or ignored, while the person record itself still syncs.

Missing Email [201]

The record has neither an email address nor a username, preventing login account creation. The run summary reports the total count of skipped accounts.

Resolution: The person record is created in Edlio, but the individual cannot sign in until an email/username is provided in the SIS. Phone-only rosters cannot authenticate without a primary identifier.

Duplicated Email [202]

Two or more records share an email address, and only one account can hold that address as a login username.

Resolution: Account creation is granted to whichever record is processed first (file order does not determine processing order). If accounts should not be created, enabling Allow duplicate emails suppresses this warning.

Invalid Email [203]

The email address is formatted improperly. Because invitation delivery and password resets depend on valid email formatting, account creation is skipped.

Resolution: Check column mapping and correct invalid email formats in the source SIS export.

Invalid Security Pin [204]

The Hall Pass security PIN is outside the permitted length of 4–16 characters. The PIN value is cleared.

Resolution: Verify mapped column and notify the district that affected staff must have valid PINs populated.

Invalid Password [205]

The supplied password fails complexity or formatting rules and is cleared. The record syncs without a password.

Resolution: Update passwords in the SIS export to satisfy system requirements, or omit password columns to allow users to set passwords via invite.

Invalid Phone Number [206]

A phone number could not be parsed and was stripped. The log message identifies the specific field.

Resolution: Check column mapping and verify that exported phone numbers adhere to standard 10-digit or E.164 formats.

Invalid Custom Attribute [207] & Invalid Custom Attribute Value [208]

  • Invalid Custom Attribute [207]: The record refers to a custom person attribute not configured for the district. The field is dropped while the record syncs. Resolution: Clean up obsolete schema mappings from deleted or renamed custom fields.

  • Invalid Custom Attribute Value [208]: The value is not among the allowed options for that attribute, or multiple values were sent for a single-select attribute (the first value is used). Resolution: Align SIS exported values with the defined dropdown options in Edlio.

Duplicated Alternate Username [209]

Two records in the same sync file claim the same alternate login identifier. Only one account receives it; others are skipped.

Resolution: Resolve identifier collisions in the SIS. Common when families share an email used as alternate username.

Did this answer your question?