How do I view CALPADS logs of data sent by Siras?
Aug 15, 2026
Use CALPADS submission history when you need to verify what SIRAS sent and how CALPADS processed it.
This is especially useful when a SIRAS-submitted transaction appears missing or blocked in CALPADS but no corresponding IVR error has appeared in SIRAS.
This article verifies the submitted job; it does not replace the normal submission cycle.
Use Reporting data to CALPADS to generate and send files. Use this article afterward when you need to inspect the CALPADS-side submission history.
Use Reporting data to CALPADS to generate and send files. Use this article afterward when you need to inspect the CALPADS-side submission history.
Quick Links
| Find the SIRAS-Submitted JobSearch CALPADS submission history using the SIRAS job and date range. | Review the Job ResultDetermine whether the job posted, rejected, or needs additional investigation. |
| What to Do NextRoute the result to investigation, correction, or reconciliation. | What to Save for SupportCollect enough job evidence to explain a missing/rejected transaction. |
Find the SIRAS-Submitted Job in CALPADS
- Log in to CALPADS.
- Go to Upload/View Submissions.
- Choose View Submission.
- Set a date range that includes when SIRAS sent the file.
- Use the available job information, including the SIRAS Job ID when applicable, to narrow the results.
- Select Apply Filter.
- Open the matching submission with the View control.
Review the Job Result
Use the submission detail to confirm:
- the file type and submission date;
- the CALPADS job status;
- whether the job posted or rejected;
- whether CALPADS provides error or validation information; and
- whether the job you found actually corresponds to the SIRAS reporting cycle you are researching.
Verification result:
You should be able to state whether the SIRAS-submitted file reached CALPADS and what CALPADS did with that job.
You should be able to state whether the SIRAS-submitted file reached CALPADS and what CALPADS did with that job.
What to Do Next
| Finding | Next step |
|---|---|
| Job posted, but the expected student/result is still missing from a CALPADS report. | Move to Reconcile. Use the applicable CALPADS report and compare the expected history with SIRAS. For 16.21 meeting history, use Find Meetings Held Late — Previously Overdue. |
| Job rejected and the reason is clear. | Use Process for Error Resolution. |
| Job rejected but the cause is not clear. | Use Data Monitoring Investigation Guide. |
| The expected SIRAS submission cannot be located. | Review the SIRAS reporting cycle, archive report status, submission order, and older blocking transactions. Start with Reporting data to CALPADS and Data Monitoring Investigation Guide. |
What to Save for Support
If the result still cannot be explained, save or note:
- SSID;
- SIRAS Job ID;
- submission date/time;
- CALPADS file type;
- CALPADS job status;
- error text or job detail when available; and
- the archive/reporting event you expected to be included.
Include this information when contacting SIRAS Support so the submission can be traced efficiently.
