Why Is This Transaction Not Sending?
| The archive is effective in the futureFuture-dated events wait until they become eligible. | Reporting-period lockThe event belongs to a different reporting period/year than the current CALPADS cycle. |
| An imported CALPADS error is posted to the archiveCorrect the IVR cause before the archive can proceed normally. | An older Pending archive is blocking a later oneWork the earlier reportable event first; submission order matters. |
| The archive should not be reportedStay Put / unagreed amendment or another non-reportable archive may need Do Not Report after verification. | None of these explain itCheck report status, components, event date, enrollment prerequisites, and submission history. |
Check the Pending Count
Go to Reporting → CALPADS Reporting and review how many archived transactions still have Pending report status.
Use the CALPADS Reporting screen to see how many reportable archives are still Pending.
Events with dates before the applicable reporting date generally need to be accounted for before certification. Use Due Dates for the current reporting timeline.
Future-Dated Archive
If the Report Event Date/effective date is in the future, the transaction can remain Pending until it becomes eligible. Verify the date is accurate; do not backdate the event merely to make it send.
Reporting-Period Lock
SIRAS/CALPADS reporting periods can prevent an event from being sent into the wrong academic/reporting year. For example, while an earlier reporting cycle is being completed, a later-year event may remain Pending until CALPADS/SIRAS rolls to the applicable period.
See Data Reporting FAQ for reporting-period-lock guidance.
Imported CALPADS Error
An archive with a posted CALPADS IVR needs the underlying problem corrected before normal resend. Use CALPADS IVR Errors Posted in SIRAS and Process for Error Resolution.
Older Pending Archive Blocking a Later Transaction
SIRAS generally needs earlier eligible reporting events to be resolved before later events can proceed. A valid Annual Plan Review, amendment, exit, or other later transaction can remain waiting because an older archive is still Pending.
An older non-reportable or unresolved Pending archive can prevent a later valid reporting event from proceeding.
- Open the student's archived transaction history.
- Find the oldest Pending event before the transaction you expected to send.
- Determine whether it should be reported, corrected, or changed to Do Not Report.
- If it has an IVR, correct that error first.
- After the older event is resolved, return to Reporting data to CALPADS.
Archive Should Be Do Not Report
An archive should not remain Pending when the underlying event is not reportable. A common example is an Other Review (Stay Put) or Addendum (Stay Put) archive representing a plan change that was not agreed to.
Diagnostic Checklist
For the oldest Pending archive, check:
- Is the Report Event Date accurate and currently eligible?
- Is a reporting-period lock preventing it from sending?
- Does the archive have an imported CALPADS IVR/error?
- Is the Report Status correct?
- Does the archive contain the expected SWDS / MEET / PLAN / SERV component?
- Does CALPADS have the required enrollment/prerequisite history?
- Should the archive actually be Do Not Report?
- If SIRAS says it sent, can the job be found with CALPADS Submission Log Help?
Use Data Monitoring Help to reconstruct the event and reporting history before changing dates or statuses.
