Workday Delta Aggregation Not Picking Up Backdated Records

Which IIQ version are you inquiring about?

8.4p3

Share all details about your problem, including any error messages you may have received.

We have been observing few issue with Workday Delta Aggregations.

Issue :
The delta aggregation is not picking up back dated records. For example:
Hire Date: 04/20/2026
Workday Record Creation Date: 04/21/2026
Delta Aggregation Date: 04/21/2026, 04/22/2026

Last Day of Work: 04/27/2026
Workday Record Creation Date: 04/28/2026
Delta Aggregation Date: 04/28/2026, 04/29/2026

These records(Hire and Terms) are not being pulled by the delta aggregation. Only the next full aggregation detects and aggregates these records.

hi @DMalaghe1993

Can you review the configuration filters such as termination offset / lookback window"

image

@DMalaghe1993 Aggregation timing could be the issue. Have you verified the timestamp of the record creation? is it prior to the aggregation task?

image

We have configured 730

Hi, a future hire date was picked, so I couldn’t see the timestamp issue.

hi @DMalaghe1993

Thanks for confirming. If the termination offset is already set to 730, the issue is likely not the offset value itself.

A few things I would suggest checking next:

  • Delta aggregation window timing: Verify how frequently deltas run and whether the Workday “last updated” timestamp for these events actually falls within the delta window. Back‑dated effective changes can sometimes have update timestamps that don’t align as expected.

  • Workday integration filters: Review any worker filters, date filters, or event filters configured on the Workday source that might exclude hires or terminations created after their effective date.

  • Change detection source: Confirm whether deltas are driven by Workday’s lastUpdatedDate vs event‑specific dates (hire/termination). This often explains why full aggregations catch records that deltas miss.

  • Extended delta / lookback testing: Temporarily extend the delta lookback (or run an extended delta) to validate whether the records are then picked up.

  • Workday API behavior: In some cases, Workday only surfaces certain historical events reliably during full refreshes.

Hi @DMalaghe1993 What have you got for pastEffectiveDateOffset?

@DMalaghe1993 Could you please confirm what are Delta_Aggregation_Events configured in your applications? You need to enable Terminate Employee event to come during Delta Aggregation. Also please confirm pastEffectiveDateOffset (like @j_place mentioned), IIQ is using it to sync back account has been set to an older date prior to the last aggregation.

<entry key="pastEffectiveDateOffset" value="30"/>

@haideralishaik how can we change detection source or extend delta/lookback testing? Do we need to do it in IIQ or Workday?

hi @neel193

In most cases, this is handled on the Workday side.

  • Detection source is driven by what Workday returns (e.g. last updated / transaction log), not something you typically change in IIQ

  • Lookback/delta behavior usually comes from Workday integration filters (RaaS / API)

So overall, it’s mostly Workday‑driven, with IIQ consuming the data.

Hope this helps.

Change detection source: Confirm whether deltas are driven by Workday’s lastUpdatedDate vs event‑specific dates (hire/termination). This often explains why full aggregations catch records that deltas miss.

Extended delta / lookback testing: Temporarily extend the delta lookback (or run an extended delta) to validate whether the records are then picked up.

Workday API behavior: In some cases, Workday only surfaces certain historical events reliably during full refreshes.

Could you explain me this briefly how can I validate those

Hi we tried,
but it didnt work

Hi @DMalaghe1993

Are you saying you have now added the pastEffectiveDateOffset - if so what value?

Also, after adding, did you do a full, followed by a delta?

Yes,
We ran full aggregation and after that create test data in lower environment and ran the Delta. but it didnt work. Below is the delta event list



Terminate Employee
End Contingent Worker Contract
Change Personal Information
Contact Information Event
Change Job
Change Legal Name
Change Business Title
Add Retiree Status
Assign Organization Roles
Change Owner
Assign Superior
EMERGENCY_CONTACT_EVENT
Change Organization Assignments for Worker
Change Primary Address
Contract Contingent Worker
Create Change Order from Contingent Worker Contract
Create Primary Address
Edit Worker Additional Data
Maintain Employee Contracts
End Additional Job
Change Marital Status
Move to New Manager
Assign Worker
Move Workers Staffing
Assign Workers
New Hire Provisioning
Change Preferred Name
Request Worker
Submit Resignation
Transfer Contingent Worker
Transfer Employee
Hire Employee
Onboarding


@DMalaghe1993 One thing to call out, Delta doesn’t support changes based on calculated/custom fields. You also please check with Workday team, if the test users which you created, comes under the events which are configured for delta or not.

Also, can you please share your workday app xml for review.

Ok, it sounds like WD is not creating Business Events for these records, so not getting picked up in Transaction Logs, so not getting picked up by Delta Aggregation. Can you confirm using Postman or equivalent?

Delta aggregation does not aggregate corrected/rescinded data.

Explanation: Delta aggregation works on business event as there is no such business event present from Workday for corrected/rescinded data. Delta aggregation does not get corrected/rescinded data.

From Troubleshooting

This is production issue not about only Test data. Yes ,I will share

Application.xml (38.2 KB)

@neel193 Did you find any Solution?