Aug 17, 2026
Verify the submitted CALPADS job Use CALPADS submission history when you need to confirm what SIRAS sent and what CALPADS did with it.
You are here: Verify.
What Do You Need to Verify?
| Find the SIRAS-submitted jobSearch CALPADS submission history by date range and available SIRAS job information. | Was the job posted or rejected?Open the matching submission and read the CALPADS job result. |
| The job posted, but the expected data is missingMove from submission verification to reconciliation with the applicable CALPADS report. | The job rejected or cannot be foundRoute the result back to investigation/correction instead of resending blindly. |
| I need to send this to SupportCapture the job ID, date/time, file type, status, error detail, and expected archive/reporting event. | |
This page verifies a submitted job. It does not replace the normal submission cycle. Use Reporting data to CALPADS to generate/send files.
On This Page
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 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.
Open Upload/View Submissions in CALPADS.
Use View Submission filters to search the date range when SIRAS sent the job.
Match the CALPADS submission to the SIRAS job/date information you are researching.
Open the submission detail to review the CALPADS job status and available error information.
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 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.
What to Do Next
| Finding | Next step |
|---|---|
| Job posted, but the expected student/result is still missing from a CALPADS report. | Move to reconciliation. Use the applicable CALPADS report and compare the expected history with SIRAS. For 16.21 meeting history, use Previously Overdue Meeting History. |
| Job rejected and the reason is clear. | Use Process for Error Resolution. |
| Job rejected but the cause is not clear. | Use Data Monitoring Help. |
| 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 Help. |
Verification complete?
Reconcile the result with the report/history that originally raised the question, then rerun the original monitoring task and return to LEA Data Monitoring Tasks.
Reconcile the result with the report/history that originally raised the question, then rerun the original monitoring task and return to LEA Data Monitoring Tasks.
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.

