An inbound EIB's results are on its integration event: the View Background Process page for the run, its Messages tab and Execution Summary, and the error files Workday attaches, including the ones you ask for with Add Errors to Attachment when you launch the EIB. Workday's public documentation does not describe a separate "error toolbar"; these are the places it does document.
If you are looking for a specific error message and what it means, use Workday EIB load errors. This page is about reading the result.
Where the results of an EIB run are
Launching an EIB (Launch / Schedule Integration) takes you to View Background Process. Click Refresh until Percent Complete reaches 100 or the Status settles. Workday's documented statuses are Processing, Completed, Completed With Errors, Completed With Warnings, Failed, Aborted and Not Run due to Exceptions on Future Process.
That page links to the integration event and the integration system, and has four tabs that matter:
| Tab | What it holds |
|---|---|
| Process Info | Actual versus scheduled start date and time |
| Process History | Date, time, status and processing time of the last five runs |
| Output Files | A link to the file the run generated |
| Messages | Detail written during the run, including the Execution Summary |
If you closed the page, run the Integration Events report to get back to the event. It lists events for an integration, and it is where the error attachments described below end up.
Read the Execution Summary first
On the Messages tab, the Execution Summary gives the completion message and the count of records processed. Compare that number to the rows in your spreadsheet before you trust the status. A status of Completed does not tell you how many records were processed; the count does.
You can also query recent runs without opening each one. The integrationEvents data source
exposes the integration system, start time, number of errors and items processed; example 14 in the
WQL cheat sheet is a ready query. That data source does not accept effective or
entry dates.
The error files Workday attaches
Workday documents error handling as attachments on the integration event. Three pieces are named in Workday's own pages:
- Add Errors to Attachment. On Launch / Schedule Integration, the Add Errors to Attachment row follows the Integration Attachment row and has a check box. Select it, and Workday creates an attachment in the Integration Events report and inserts comments in the key fields of the rows that have errors.
- Failure Report and Errors and Warnings spreadsheet. Workday's limits page lists FailureReport.html, ErrorsAndWarningsSpreadsheet.xml and OriginalDataWithErrors.xml as the troubleshooting files an inbound EIB produces.
- Retention. Those three files are kept for 60 days. Pull a copy if you need the evidence for longer. Spreadsheet attachments themselves have no retention limit and stay on the event.
Workday's public pages do not describe the layout of the Failure Report or how to turn each file on separately, so open one from a real run in a Sandbox tenant to see what your tenant produces.
Fix and reload only the failed rows
Workday's documentation does not prescribe a procedure for a partial reload, so this is practice, not documentation:
- Open the error attachment and note each failing row with its message.
- Work out whether the good rows loaded. The Execution Summary count against your row count tells you, and so does opening one of the records you sent.
- Copy only the failed rows into a fresh spreadsheet from the same template. If the template has changed, regenerate it with Template Model > Generate Spreadsheet Template from the EIB's related actions; Workday requires an XLSX for the Extend business object loads it documents.
- Run the one-row or few-row file first. Launch it with Add Errors to Attachment selected again so a repeat failure explains itself.
- Only then send the rest.
Do this in a Sandbox first. Reloading a row that already succeeded is a different problem from reloading one that failed, and what happens depends on the web service the EIB calls.
Launch and schedule options that exist
Workday documents these on Launch / Schedule Integration:
- Run Frequency. Choose Run Now or a schedule.
- Integration Attachment. Where you pick the spreadsheet, or use Create Integration Attachment to upload it. Browser uploads are limited to 30 MB.
- Add Errors to Attachment. The error comments described above.
- You cannot launch an integration system that has Critical errors.
Workday's public documentation describes no validate-only mode for inbound EIBs. The way to test a load without risking production data is to run it in an Implementation or Sandbox tenant; see refreshing a Workday Sandbox if yours has drifted.
Time limits that explain a stuck run
Workday gives an inbound EIB loading web-service or custom-object data five hours. Creating the Failure Report, the Errors and Warnings spreadsheet and the Add Errors to Attachment spreadsheet has its own two-hour limit, so a large file can load and still be waiting on its error files. Up to five integrations run at once, and Workday suggests an odd start time such as 9:10 over the top of the hour to avoid queuing.
If the EIB reads a report as its source, the report must be enabled as a web service first; see how to set up Workday RaaS.