The Department of Education discovered yesterday that IDSA25OP and IGSA25OP, two ISIR message classes, were accidentally replicated and sent to the SAIG mailboxes numerous times. In response, ISIR transmissions along with the duplicate files were temporarily suspended to prevent institutions from receiving inaccurate data while officials researched the cause of the issues.
As of this morning, April 18th, FSA stated that they resolved the problem and begun transmitting ISIRs to SAIG mailboxes again.
Read the complete announcement below.
POSTED DATE: April 17, 2024
AUTHOR: Federal Student Aid
ELECTRONIC ANNOUNCEMENT ID: GENERAL-24-43
SUBJECT 2024–25 FAFSA ISSUE ALERT: Replicated ISIRs Delivered to FTI-SAIG Mailboxes on April 16, 2024 (Updated April 17, 2024)
On April 16, 2024, between 3:45 and 8:30 p.m. Eastern time (ET), 2024–25 Institutional Student Information Records (ISIRs) in the messages classes IDSA25OP and IGSA25OP were inadvertently replicated and delivered to federal tax information (FTI)-Student Aid Internet Gateway (SAIG) mailboxes multiple times.
We took the following actions immediately in response to the issue:
- We temporarily ceased transmission of ISIRs to FTI-SAIG mailboxes until we fully research and resolve the issue.
- We disabled the replicated ISIR files. This means that they are no longer viewable in the mailbox.
The impact of this issue to schools, state agencies, software vendors, and third-party servicers is outlined below.
For a school or organization that did not access its FTI-SAIG mailbox or did access its mailbox but did not see replicated ISIRs on Tuesday, April 16, no action is needed.
For a school or organization that did access its FTI-SAIG mailbox and saw replicated ISIRs on Tuesday, April 16, the following action is needed:
- Look for ISIR files with the timestamp “16:23:45 ET”.
- Check all ISIR files with that timestamp and ensure that the information across all files is exactly the same.
- Use only one of the replicated ISIR files to proceed with packaging aid.
Today, we are focused on identifying a resolution to the issue and restarting ISIR delivery. We appreciate your patience and will update the issue status later today.