It looks like a Dayforce bug. An employee was added to the erase queue — maybe for a GDPR cleanup, a termination, or a data hygiene project — but before the deletion processed, someone rehired them or manually updated their status. Now Dayforce shows the employee as active, but the erase flag is still queued. The profile is frozen. Payroll won't run on it. Nobody can explain what happened.
This is one of the most confusing edge cases in Dayforce administration, and it's almost entirely a timing problem. Here's what's actually going on and how to fix it.
What the conflict actually is
Dayforce has an erase queue — a background process that processes deletion requests for employee records. This queue exists to handle GDPR right-to-erasure requests, mass data cleanup initiatives, and standard termination workflows where records are removed on a scheduled basis.
When an employee is added to the erase queue, a deletion flag is set on their profile. This flag sits in a processing queue and executes on Dayforce's schedule — not immediately, and not always predictably. If someone reopens that employee's record, changes their status to active, or processes a rehire before the erase job runs, you end up with a profile that has two conflicting states: an active employment status and a pending deletion flag.
Dayforce doesn't reconcile these states automatically. The result is a profile that appears usable but is functionally locked: the employee won't appear correctly in payroll runs, self-service access may be broken, and any attempt to update core employment data throws a validation error.
Why this happens
Need hands-on help with Dayforce?
Talk to our team →The root cause is almost always a gap between two separate workflows that don't communicate with each other.
First: the erase queue typically runs on a batch schedule — nightly, weekly, or on an admin-defined cycle. If your HR team doesn't know when the queue processes, it's easy to make a manual update to a record that's already been queued for deletion.
Second: rehire workflows in Dayforce often don't check for pending deletion flags. A manager submits a rehire request through the standard onboarding flow, the employee record is reactivated, and nobody realizes the deletion flag is still active in the queue until payroll runs — or doesn't.
Third: during GDPR compliance projects, it's common for HR teams to add large groups of former employees to the erase queue without cross-referencing against the rehire pipeline. A record that should have been excluded because the employee was in discussions for a return gets caught in the batch.
The conflict is a process gap, not a Dayforce defect. Dayforce is doing exactly what it was told: processing a deletion request and reactivating a profile. The problem is that two teams — or two workflows — gave it conflicting instructions.
How to fix it
Struggling with Dayforce Consulting?
Harmon & Co specializes in Dayforce consulting for mid-market companies. We fix it the first time — no endless ticket queue, no generic advice.
