Every data sync or import into Edlio produces an execution log. When issues arise, understanding how to read the log and distinguishing between warnings and fatal run failures ensures sync errors are diagnosed quickly and accurately.
How to read the sync log
Each entry in the sync log contains four key components:
Error Type: The name and numeric identifier representing the issue category.
Data Type: The role or entity concerned (e.g.,
Student, configured parent, staff, community roles,Classroom, orGeneralfor the whole run). It represents a role grouping, never a specific individual person.Severity: Indicates the impact level (
Error,Warning, orInfo).Message: Detailed technical information. Where a specific record is identified, it follows a structured format:
Name: ..., followed bySourceId: ...(orNo SourceId),Email: ...(orNo Email), and for file-based feeds:From File: {name}, Row: {n}.
Important log behaviors to keep in mind:
General Error [100] and General Warning [50] counts can be inflated: Any stored message written without an explicit error type is defaulted to General Error or General Warning when read back. Always evaluate the specific message text rather than the error type name alone.
Internal vs. District-Visible Logs: Certain low-level system failures are recorded internally for Edlio engineering only and do not appear in the district-facing log.
Severity is not fixed per error type
The error type does not dictate whether the sync run failed — the severity does.
Error: Halts the sync for that data type/role, marking the run as failed.
Warning: An individual record or field was skipped, cleared, or ignored, while the rest of the sync completed successfully.
The same error type can arrive at different severities depending on context:
File Read Error [52]: Warning when a single file fails to parse and is skipped; Error when the file listing or SFTP fetch itself fails.
Missing Source ID [101]: Warning when a classroom row lacks an ID, or when a person row lacks an ID and Skip Records with missing Source Id is enabled; Error when a person row lacks an ID and that option is disabled.
District ID Mismatch [305]: Warning when cross-district connect is disabled (account excluded); Info when cross-district connect is enabled (steady state).
Invalid Organization [403]: Warning when a single person row maps to no organization; Error when a configured organization ID is outside the district.
Conflicting Options [500]: Warning for an unsupported relationship type or when app accounts are skipped because login is disabled; Error when an app or dashboard account is configured with a missing ID.
Run and delivery outcomes
These outcomes occur at the delivery stage before individual records are evaluated:
General Warning [50]
A catch-all warning: a classroom with no name, a classroom sharing a SourceId with conflicting data, a username or alternate username exceeding length limits (value is cleared), a failed people-index rebuild, or a password update that did not take.
Resolution: Read the specific message text — the error type carries no inherent meaning on its own.
No Files Found [51]
No files arrived for the account, or none arrived for a particular role. Nothing was synced, and Edlio retains whatever data the last successful run left.
Resolution: Confirm the district's SIS export ran, exported to the correct SFTP folder, and that file names match the schema fragment match rules (Edlio matches on name fragments, not full strict names). Because feeds that quietly stop delivering leave rosters stale without other signals, this triggers notifications to all subscribers.
File Read Error [52]
A file could not be read and was skipped, or the SFTP listing failed.
Resolution: The message identifies the file and parse error (e.g., missing header row, altered delimiter, truncated upload). Request a clean re-export. If the directory listing itself failed, verify SFTP credentials and server permissions rather than file contents.
No Records Found [53]
Files arrived and parsed cleanly, but contained zero records for a configured role.
Resolution: Verify whether the export still includes that group. If a district stops sending staff, this warning appears for staff while students continue syncing. Existing records are not removed; data remains as it was.
Infrastructure & status markers
Timeout [600]
A database call did not answer in time. This indicates an Edlio infrastructure condition, not invalid district data. It is separated from General Error so it can be recognized immediately without reading stack traces. Raised when reading existing classrooms times out; affected classrooms are skipped while the rest of the sync proceeds.
Resolution: No action required by the district. A single occurrence can be safely ignored; repeated occurrences should be escalated to the dev team to inspect missing indices or site sizing.
Status [900] & Validation Info [910]
These are informative audit markers rather than errors:
Status [900]: Records per-stage counts of inserted, updated, and deleted records for people, accounts, classrooms, and relationships. For classrooms, also notes legitimate term rollover replacements.
Validation Info [910]: Identifies records intentionally left untouched because they are marked edit-protected or delete-protected in the dashboard.