Skip to main content

Activity Log & Connect Settings

The E-Brake is a safeguard built into Campus Management in the Settings tab that prevents large, unexpected changes from being processed during daily data syncs. By setting a maximum change percentage for each file, you can ensure that only expected volumes of data are ingested, and that any files that would change beyond that threshold is not synced.


How the E-Brake works

Each time a file is sent through a sync, Campus Management calculates the percentage of rows that represent a change, either new data or updated data. If that percentage exceeds the maximum you've set, the sync is halted for that file, protecting your data from unintended mass updates.


What to do if the E-Brake activates

  1. Check the Activity Log to identify which file shows a red warning symbol and what change percentage was detected.

  2. Review the incoming file from your SIS or district to confirm whether the volume of changes is expected.

  3. If the changes are valid and expected, adjust the Max percentage in Settings to accommodate the incoming data, then if possible resend the file again.

  4. If the volume of changes looks unexpected or incorrect, investigate the source file before allowing the sync to proceed.



Types of Connect Files

  • Student

  • Staff

  • Guardian

  • Room/Classes (Roster)

  • Enrollment


Configuring the E-Brake in Settings

To set your maximum change percentages, go to Campus Management → Settings. Under Set maximum change percentage, you'll find a Max percentage field for each file type.

Change Value

What it does

--

No block is in place, any amount of change in a file will be accepted.

1-99%

The maximum percentage of rows allowed to change per file, per sync. If the incoming file exceeds this threshold, the sync for that file type will be halted.


Reading the E-Brake in the Activity Log


After each sync, the Activity Log shows a summary for each file type processed. This is where you can see whether the E-Brake was a factor in the sync.

If no file export appears in the Activity Log after a sync should have occurred, the file may not have been processed check whether anything has changed on the SIS export side, such as an updated file name, change in headers, or file change to file extention.

Each file type entry in the Activity Log displays:

Column

What it shows

File type label

The name of the file (e.g. Connect) along with the current E-Brake limit in parentheses, e.g. Connect (Limit: 50%)

Change percentage

The actual percentage of changes detected in the incoming file, displayed beneath the file type label

Total rows

Total number of rows in the incoming file

Ingested rows

Rows successfully processed and applied

Invalid rows

Rows that could not be processed due to data issues

New rows

Rows representing newly added records

Changed rows

Rows representing updates to existing records

If the detected change percentage is below the limit, the sync proceeds normally and rows are ingested. If the change percentage meets or exceeds the limit, the E-Brake activates and the file is not processed. If this occurs, the Ingested, New, and Changed rows will show 0.


E-Brake Example

If the Connect file type has a limit of 50% and an incoming sync shows a 0% change rate, the sync completes successfully. However, if a future sync sends a file where 60% of rows have changed, the E-Brake would activate, and no rows would be ingested until the limit is reviewed or adjusted.

Did this answer your question?