10.3 Troubleshooting EIB Data Loads & Access Issues

Workday Pro Platform Administrator Certification Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The Workday Platform

1.1 Workday Products, Functional Areas & Product Touchpoints 1.2 The Object Management Model & Business Objects 1.3 Navigation & Search Techniques 1.4 Organizations in Workday

2 Chapter 2: Tenants & Release Management

2.1 Tenant Types & Tenant Management Tasks 2.2 Releases, Adoption, System Testing & Support

3 Chapter 3: The Configurable Security Framework

3.1 Components of the Configurable Security Framework 3.2 Core Security Group Types: Workday-Assigned, User-Based & Role-Based 3.3 Advanced Security Group Types

4 Chapter 4: Security Policies, Assignment & Troubleshooting

4.1 Domain Security Policies & Permissions 4.2 Assigning Roles & Security Group Membership 4.3 Troubleshooting Security Access Issues

5 Chapter 5: Business Process Definitions & Steps

5.1 The Business Process Framework & Definitions 5.2 Business Process Step Types 5.3 Step Configuration, Order & the Completion Step

6 Chapter 6: BP Security, Condition Rules & Troubleshooting

6.1 Business Process Security Policies 6.2 Creating & Testing Condition Rules 6.3 Using Reports to Troubleshoot Business Processes

7 Chapter 7: Report Foundations & Custom Reports

7.1 Business Objects, Fields, Related Business Objects & Data Sources 7.2 Standard Reports, Custom Report Types & the Report Writer 7.3 Worklets, Dashboards & Sharing Reports

8 Chapter 8: Calculated Fields, Alerts & Report Administration

8.1 Identifying & Maintaining Calculated Fields 8.2 Configuring & Testing Alerts 8.3 Scheduling Reports, Report Groups & Transferring Ownership 8.4 Troubleshooting Report Data & Access Issues

9 Chapter 9: Integration Architecture & Security

9.1 Workday Integration Architecture & Web Services 9.2 Workday Integration Tools & Choosing the Right One 9.3 Integration System Users & Integration System Security Groups

10 Chapter 10: Enterprise Interface Builders

10.1 Creating & Launching an Inbound EIB 10.2 Creating & Launching an Outbound EIB 10.3 Troubleshooting EIB Data Loads & Access Issues

10.3 Troubleshooting EIB Data Loads & Access Issues

Key Takeaways Explain This Topic AI

Start at the integration event, which records the run, its status, and the messages produced for each row.

Distinguish a whole-run failure, which usually indicates security, connectivity, or template structure, from row-level failures, which usually indicate data.

Row-level errors on an inbound EIB are typically validation failures, invalid reference IDs, missing required fields, or business process routing problems.

Correct the failing rows in the spreadsheet and reload only those rows, rather than reloading the entire file and duplicating successful transactions.

Use Process Monitor for the status of scheduled and background integration processing, and the standard security troubleshooting method for access errors.

Last updated: August 2026

Diagnose in this order 1. INTEGRATION EVENT → did it run? what status? what messages?

2. SCOPE → whole run failed, or individual rows?

• 3. WHOLE RUN → security · connectivity · template structure
• 4. ROW LEVEL → data · validations · business processes
• 5. FIX & RELOAD → correct rows only, never the whole file again

Every EIB launch produces an integration event recording the run, its status, and the messages generated. It is the first thing to open and it usually names the cause directly.

For scheduled integrations, Process Monitor shows the status of background and scheduled processing. Use it when an integration was expected to run and there is no integration event at all - that is a scheduling problem, not an integration problem.

Whole-run failures

When nothing processed, the cause is structural.

Symptom Likely cause Fix

Authentication failure ISU password expired, or the account is locked Reset and exclude the ISU from password expiration; confirm Do Not Allow UI Sessions is set but Require New Password at Next Sign In is not

Access error before any row processes ISSG lacks Get or Put on a required domain, or the policy change was never activated Run View Security for Securable Item on the item named in the message, then View Security Groups for User on the ISU; grant and activate

Template rejected Columns added, removed, or reordered; wrong web service operation Regenerate the template from the integration system and repopulate it

Delivery failure with a successful extract SFTP credentials or host key rotated; endpoint unreachable Update delivery configuration; verify the endpoint

Nothing ran at all Schedule not active, or the scheduled run failed to start Process Monitor

The distinction that saves the most time: an extract that succeeds with a delivery that fails is a connectivity problem, and the data is fine. An access error before any row processes is a security problem, and no data was touched. Neither requires looking at the spreadsheet.

Row-level failures on an inbound EIB

When some rows succeed and others fail, the cause is in the data - because, as section 10.1 established, an inbound EIB performs the same transactions a user would , and it therefore hits the same validations.

Message pattern Cause Fix

Instance not found / invalid reference A reference ID does not exist or is misspelled Correct the ID. Use reference IDs, not display names

Required field missing A required column is blank Populate it; the template marks required fields

Validation error A validation condition on the business process rejected the data Correct the data, or confirm the validation is intentional

Effective date error The date precedes a dependency, or falls outside a permitted range Correct the effective date

Data type or format error Dates or numbers reformatted by the spreadsheet application Reformat the column and reload

Business process error The transaction routes through a business process the account cannot initiate, or a step has no assignee Check the BP security policy and the role assignment on the organization

• Duplicate The record already exists Remove the row, or use the correct update operation
• The reload discipline

Correct the failing rows and reload only those rows.

Reloading the whole file re-processes every row that already succeeded. Depending on the operation that produces duplicate records, re-triggered business processes, or a second round of notifications to everyone involved - and unwinding that is far more work than the original load. Build the corrected file from the failures only.

Access errors, resolved the same way as everywhere else

EIB access errors use the identical method from section 4.3, with the ISU in place of a person:

Read the message and identify the securable item.

View Security for Securable Item on that item - which domains secure it, which groups are permitted.

View Security Groups for User on the ISU - which ISSGs is it in?

Grant the ISSG Get (read) or Put (write) on the domain.

Activate Pending Security Policy Changes.

Relaunch.

Two mistakes to recognize instantly. Granting View and Modify to an ISSG instead of Get and Put - the account authenticates and the integration still fails. And skipping activation - everything looks configured and nothing is live.

The silent failure: incomplete output

The hardest EIB problem produces no error at all.

An outbound EIB with a constrained ISSG returns only the instances that account can see. Workday reports success, the file is delivered, and it is incomplete. Similarly, an integration using change detection legitimately sends only what changed - an empty file may be entirely correct.

Before treating a small output as a defect:

Run the underlying report interactively as a fully privileged user and compare the row count.

Check whether the ISSG is constrained, and to which organizations.

Establish whether the integration uses change detection .

Check the report's own filters and any data source filter , using the reporting method in section 8.4.

Symptom-to-cause quick reference

• Symptom Start here
• No integration event exists Process Monitor - scheduling
• Authentication failed ISU password and account settings
• Access error, nothing processed ISSG permissions - Get/Put - and activation
• Template rejected Web service operation and template structure
• Some rows failed Row messages on the integration event - data and validations
• Rows failed with routing errors BP security policy and organization role assignment
• Extract fine, delivery failed Endpoint credentials and connectivity
• Delivered but incomplete, no error Constrained ISSG, change detection, or report filters
• Wrong columns or wrong order The report definition, for an outbound EIB
• Escalating beyond EIB

Sometimes the correct answer is that EIB is the wrong tool. Return to the ordered guidance in section 9.2: if the requirement needs per-object processing , multiple web service calls per object , complex error handling and logging , multiple output files , or custom error and warning messages , then a connector with Document Transformation , Orchestrate , or Workday Studio is the intended tool. The Platform Administrator objective is to support basic integrations using Enterprise Interface Builders - and recognizing the boundary of "basic" is part of that objective, not a gap in it.