Skip to main content

Data Logs: Monitoring Sync History, Errors, and Warnings

How district administrators can review sync run history, examine errors and warnings, and export diagnostic logs in the Edlio App dashboard.

Edlio’s Data Logs dashboard provides complete transparency into every Student Information System (SIS) sync and file import executed for your district. Located in the Edlio App dashboard under Data Logs (/next/app/data-logs), it consolidates run history, error and warning trends, read files, and row-level diagnostic messages so administrators can quickly diagnose roster issues.

Data Logs dashboard in Edlio App showing run selector, summary cards, and error table

Video walkthrough: Data Logs overview

Video chapters & timestamps

  • 0:00 - Introduction to data hygiene & Data Logs: Why monitoring sync health ensures the Edlio App and Mass Communication always operate with accurate district rosters.

  • 0:35 - Data integration sources & trends graph: Distinguishing between SIS API, SFTP, and manual imports, and tracking error/warning trends across historical ingestion runs.

  • 1:10 - Reviewing files & the diagnostic table: Viewing and downloading files read during a run, and opening row-level items to inspect exact data errors.

  • 1:43 - Error vs. warning severity mechanics: How errors completely halt record ingestion (e.g. duplicate Source IDs between Ava and Mateo), while warnings import the record but omit invalid fields (e.g. duplicate parent emails).

  • 3:22 - Filtering & sorting issues: Using filters to isolate specific severities (Error vs. Warning), error types (invalid emails), or data roles (Students, Teachers, Parents).

  • 3:51 - In-app Error Reference catalog & exporting logs: Accessing built-in error definitions and downloading CSV logs to share with your SIS vendor or database team.

  • 4:26 - Historical run selector & resolving issues upstream: Switching between today's run and past runs to verify error counts decrease to zero after fixing data in your SIS.

Key takeaways from this video

  • Your SIS is always the source of truth: Edlio never modifies or overwrites data in your SIS. When an error or warning appears in Data Logs, correct the student, parent, or staff record upstream in your SIS so subsequent syncs ingest clean data.

  • Errors halt records, warnings adjust fields: A record flagged with an Error (such as a missing or duplicated Source ID) is completely excluded from Edlio until fixed. A record with a Warning (such as a duplicated email or invalid phone) is successfully created, but the problematic field is omitted.

  • Multi-source tracking: If your district runs both direct SIS API syncing and SFTP CSV feeds, or uploads manual classroom rosters, Data Logs isolates each source so you immediately know where the discrepancy originated.

  • Direct SIS vendor collaboration: Use the Export button to generate a clean CSV of all row-level error codes and forward it directly to your IT database team or SIS provider for rapid resolution.

Understanding the Data Logs dashboard

When you open Data Logs, the dashboard displays metrics for the most recent sync run:

  • Access Permissions: Viewing Data Logs requires the View Data Logs permission (assigned by default to the "SIS Integration Only" account type, or enabled on district admin profiles).

  • Run Selector: A dropdown at the top showing the timestamp and trigger method of the selected run (e.g. Jul 24, 2025, 8:39 PM · automated nightly or triggered by an administrator). Click the selector to review historical runs across recent days and months.

  • Errors Summary Card: Displays the total count of records that could not be brought into Edlio during this run.

  • Warnings Summary Card: Displays the count of records that came in successfully, but with something missing, truncated, or adjusted (such as invalid formatting on an optional field).

  • Files This Run Read: Lists all file bundles received and processed during file-based imports. When files are delivered, administrators can inspect which files arrived and download the source archives directly. Note: Below the files card, the diagnostic record list shows users/records flagged with errors or warnings during the run.

  • Errors & Warnings Chart: A visual timeline tracking error and warning counts across recent sync executions, making it easy to identify data spikes following term rollovers or SIS re-exports.

Reviewing and filtering row-level records

Below the summary cards, the diagnostic table lists individual records requiring attention:

  • Name: The student, staff member, or classroom name identified in the incoming record.

  • Data Type: The role or entity grouping concerned (e.g. Student, Staff, Parent, or Classroom).

  • Email: The associated email address from the record (or No Email).

  • School: The campus or organization associated with the record.

  • Error Type: The specific classification of the issue (e.g. Missing Source ID, Duplicated Email, Invalid Phone Number).

  • Severity: Marked as Error (record halted/excluded) or Warning (record imported, field adjusted/skipped).

Search and Instant Filter: Use the search bar to locate specific individuals by name, email, or message text. Click Filter to narrow the report by severity level, role, or school campus.

The in-app Error Reference catalog

Clicking the Learn More About Errors button at the top of Data Logs opens the built-in Error Reference catalog directly inside the dashboard:

Error Reference catalog modal in Data Logs detailing sync error types and resolutions

The catalog provides instant definitions and resolution advice across all sync error codes:

  • Run & Delivery Outcomes (IDs 50–53): Covers delivery-level events such as No Files Found [51] (export didn't deliver or directory changed), File Read Error [52] (malformed headers or corrupted CSV), and No Records Found [53] (group omitted from export).

  • Record Identity Errors (IDs 100–104): Identifies unique identifier collisions including Missing Source ID [101], Duplicated Source ID [102], Duplicated Employee ID [103], and Duplicated Student ID [104].

  • Field Validation Warnings (IDs 201–209): Highlights format discrepancies that skip account creation or drop fields without halting syncs (e.g. Missing Email [201], Duplicated Email [202], Invalid Phone Number [206]).

  • Data Conflicts & Safety Thresholds (IDs 301–306, 404): Details profile collisions and the critical Large Scale Threshold Reached [404] safety guard that pauses automated database modifications when mass deletions or replacements are detected.

Exporting log reports for your SIS team

Clicking the Export button downloads a comprehensive CSV of all diagnostic messages for the selected run. District administrators can forward this export directly to their district SIS or IT database team to correct source records before the next scheduled nightly sync.

💡 Best-practice sync workflow: After correcting duplicate IDs or invalid email formats in your SIS, navigate to Data Setup and click Sync Now. Once the sync completes, return to Data Logs to verify that the error count has dropped to zero.

Related articles

Did this answer your question?