What Did the Aeries Completion Email Show?
| Match Updated RecordsStudents matched and Special Education information updated. | Type A Unmatched RecordsA student row could not be matched between SIRAS and Aeries. |
| Type A Unmatched Not in FileAeries expects an active Special Education student who was not in the SIRAS student file being processed. | Type B Unmatched RecordsA service row could not be matched to the applicable student record. |
| No completion email arrivedConfirm the job ran and the current monitoring recipients are configured. | A student exit still looks wrongCheck whether the applicable inactive/exit record was actually present in the SIRAS export population. |
Understand the Aeries Report Names
Aeries completion reports may still use legacy CASEMIS Type A / Type B terminology. Treat these as operational report names for the current Aeries Special Ed Data Import process.
| Aeries report | What it means | What to do next |
|---|---|---|
| CASEMIS Type A Match Updated Records | Student records matched and the Special Education information was successfully updated in Aeries. | Review the count and spot-check representative or high-impact changes. An unexpectedly small or large count should be investigated. |
| CASEMIS Type A Unmatched Records | Student records could not be matched between the systems. | Review the student's identifiers and determine whether the SIRAS record, Aeries record, or source data needs correction. |
| CASEMIS Type A Unmatched Not in File | Aeries shows the student as active in Special Education, but the student was not present in the SIRAS student file being processed. | Review SIRAS Current/status/history and the applicable SIRAS export population. Do not assume the student should simply be added back to the file. |
| CASEMIS Type B Unmatched Records | A service row could not be matched to the applicable student record. | Resolve the related Type A/student problem first. Service warnings often clear after the student match is corrected. |
Match Updated Records
CASEMIS Type A Match Updated Records is the expected successful-match report. It means the student row matched and Aeries accepted the Special Education update.
Do not review only whether the file exists. Look at the count and spot-check records when the result is unexpected, when a high-impact change occurred, or when the district is validating a new/changed integration.
Type A Unmatched Records
This report means the student row could not be matched between SIRAS and Aeries. Start with the identifiers represented in the two systems rather than manually forcing the Special Education value to match.
For a student-level mismatch, use SIS Integration Troubleshooting & Ongoing Monitoring to review matching, identifiers, source rows, duplicate/ambiguous records, and field authority.
Type A Unmatched Not in File
This result means Aeries shows the student as active in Special Education, but the student was not present in the SIRAS student file that Aeries processed.
Review:
- the student's current SIRAS status;
- the applicable archived/history record when the student previously exited or transferred;
- whether the student should have been in the SIRAS export population for that run; and
- whether Aeries still contains an older active Special Education status that requires follow-up.
Type B Unmatched Records
Type B represents service information. If the service row cannot be matched to a student, resolve the related student/Type A problem first. After the student match is corrected and the import is rerun, the service warning may clear with it.
No Completion Email Arrived
If the expected completion email did not arrive:
- Confirm that the Aeries scheduled/manual Special Ed Data Import actually ran.
- Confirm that the current responsible staff are entered as completion-report recipients in Aeries.
- If the job itself did not run or retrieve the SIRAS files, use SIS Integration Troubleshooting & Ongoing Monitoring.
- If the problem is the SIRAS SFTP connection, use SIRAS SFTP: Secure File Exchange & Connection Settings.
For initial setup of recipients and the one-time connection test, use Aeries–SIRAS Integration: Configure and Test Both Data Directions.
A Student Exit Did Not Reach Aeries
Older exit / inactive record
An older inactive/exit record may no longer be present in a current SIRAS export, depending on the export population and the timing of the underlying event. Verify the SIRAS record and archive/history first. If the correct historical exit is outside the current file population while Aeries still shows the student active in Special Education, Aeries may require a manual correction.
Very recent exit
If a student was made Inactive and then transferred away or changed program/module before the nightly file was created, verify whether the Inactive record actually appeared in the applicable SIRAS export. Use SIS Integration Troubleshooting & Ongoing Monitoring when the file history or job evidence needs review.
Remember Which Integration Direction You Are Reviewing
| Direction | Primary monitoring evidence | Help |
|---|---|---|
| Aeries → SIRAS | SIRAS Scheduled Task Logs and the current api_import_log.csv. |
SIS Integration Troubleshooting & Ongoing Monitoring |
| SIRAS → Aeries | Aeries Special Ed Data Import completion email and attached reports described on this page. | Read the Aeries Completion Email & Reports |
Use Aeries–SIRAS Integration: Configure and Test Both Data Directions. For the SIRAS SFTP host, port, username, password, manual connection test, or firewall troubleshooting, use SIRAS SFTP: Secure File Exchange & Connection Settings.
