---
title: "Workday Open Enrollment On Hold: Backdated Change Fix"
description: "A backdated job or life event makes Coordination of Events hold Open Enrollment, then rescind and recreate it. Where to look in Benefit Election History."
url: https://kiweely.com/guides/workday-open-enrollment-stuck-disappeared-elections
---

# Why is a worker’s Workday Open Enrollment On Hold or missing after a backdated change?

A backdated life event or staffing change triggers Coordination of Events, which puts the later Open Enrollment event On Hold until the earlier event completes, then rescinds and recreates it. Finish or cancel the earlier event in Benefit Election History.

-   **Checked** against Workday on November 19
-   Applies to **Workday Benefits**
-   8 min read
-   Published November 13
-   By Kiweely

When a worker’s Workday Open Enrollment task disappears from **My Tasks** or freezes in **On Hold** status after a backdated **Change Job**, address update, or life event, **Coordination of Events** is holding the future-dated Open Enrollment record behind an unfinished earlier-dated benefit event. Open the worker’s profile, select **Benefits > Benefit Election History** (or **View Benefit Election History**), and complete, finalize, or cancel the earlier-dated **In Progress** benefit event so Workday can rescind the held record and generate a clean Open Enrollment event.

Checking one worker takes two minutes; finding every stuck **On Hold** record across a fourth-quarter reorganization takes an audit report and row-by-row history checks. **[Kiweely Vine](https://kiweely.com/download)**, a desktop AI agent for Mac and Windows, inspects live business processes, benefit configurations and security in your tenant and builds custom audit reports and calculated fields from a plain question ([download Kiweely Vine free](https://kiweely.com/download)).

During fall Open Enrollment, this collision happens constantly because Open Enrollment carries a future **Event Date** (typically January 1 of the upcoming plan year), while day-to-day HR and life events carry October, November, or December effective dates. Workday processes benefit enrollment events strictly in **Event Date** order, comparing two events at a time to protect coverage continuity.

## Why Does a Backdated Change Put Open Enrollment On Hold or Wipe Elections?

Whenever you initiate **Change Benefits**, complete a staffing transaction mapped to a benefit event (such as **Change Job**, **Change Primary Address**, or **Propose Compensation Change**), or run passive events, Workday compares the newly created benefit event against any later-dated benefit event on the worker’s record.

text

```
Timeline Example During Fall Open Enrollment:
- Nov 01: Open Enrollment starts with Event Date = 2027-01-01 (Status: In Progress or Submitted)
- Nov 12: HR enters a backdated Promotion or Address Change effective 2026-11-01
- Result: Workday creates a 2026-11-01 Benefit Event -> places 2027-01-01 Open Enrollment "On Hold"
- Unblock: Complete or cancel 2026-11-01 Benefit Event -> Workday rescinds held OE and creates a new 2027-01-01 OE event
```

Workday places the January 1 Open Enrollment event **On Hold** and forces reprocessing whenever either of two conditions is true:

1.  **Benefit eligibility or Benefit Group changes.** The backdated **Change Job**, location transfer, FTE change, or leave return causes the worker to gain coverage eligibility, lose coverage eligibility, or move into a different **Benefit Group**. Workday *always* reprocesses later events on an eligibility change.
2.  **Coverage types overlap without reprocessing overrides.** The November life or staffing benefit event offers at least one **Benefit Coverage Type** (for example, Medical, Dental, or Basic Life) that also exists in the January 1 Open Enrollment event, and neither event type has **Do Not Reprocess** or **Do Not Reprocess Future Events** enabled.

Once the earlier-dated November event finally completes (or is finalized by an administrator), Workday **rescinds or cancels** the **On Hold** Open Enrollment event and creates a brand-new Open Enrollment event dated January 1. Workday calculates the worker’s new **Submit By** deadline by adding **Days to Enroll** (under **Coordination of Events** on the event type) to the creation date of the recreated event.

## Which Diagnostic Symptom Matches Your Worker’s Record?

Before touching elections manually, inspect **Benefits > Benefit Election History** on the worker profile and match the exact row statuses against these four failure modes:

| What You See in Workday | Exact Root Cause | Where to Verify and Fix |
| --- | --- | --- |
| Open Enrollment row shows **On Hold**; worker no longer sees **Enroll in Benefits** in **My Tasks** | An earlier-dated life, staffing, or passive benefit event is still **In Progress** or awaiting approval ([business process awaiting action](https://kiweely.com/guides/business-process-awaiting-action)) | Locate the earlier-dated event in **Benefit Election History**; have the worker submit it, run **Finalize Open Benefit Event Elections**, or cancel/rescind it if created in error. |
| Worker submitted Open Enrollment last week, then received a brand-new Open Enrollment task today | Earlier-dated benefit event completed, causing Coordination of Events to rescind the original Open Enrollment and generate a new January 1 event | Open the newly created Open Enrollment event; verify whether newly gained plans or changed Benefit Group rates require the worker to review and click **Submit** again. |
| Worker disappeared from Open Enrollment completely or cannot be re-added | Backdated job or location move placed the worker in **zero** eligible Benefit Groups, or in **two** Benefit Groups simultaneously | Run **Benefits Eligibility by Worker** as of January 1 and **View Workers in Multiple Benefit Groups Audit** (a worker can belong to only one Benefit Group). |
| January 1 promotion or life event failed to merge with January 1 Open Enrollment (or canceled a January 1 life event) | Workday consolidates same-day staffing and life events into a hybrid event, **except** events coinciding with Open Enrollment | Never date a non-Open Enrollment benefit event on the Open Enrollment event date; if Open Enrollment already exists on January 1, enter the non-OE benefit event on another date. |

Web service benefit loads need explicit Coordination of Events activation

If inbound integrations create earlier-dated benefit events via the **Change Benefits** web service while Open Enrollment is active or future-dated, Workday only reprocesses eligible future-dated events when **Enable Coordination of Events for the Change Benefits Web Service** is selected in the **Benefits** section of **Edit Tenant Setup - HCM**.

## Step-by-Step: Unblocking a Stuck Open Enrollment Event Without Corrupting History

Follow this sequence so you do not leave orphaned **In Progress** benefit events or accidentally overwrite carrier history:

1.  **Inspect `Benefit Election History` first.** Navigate to the employee’s profile, open **Related Actions > Benefits > Benefit Election History**, and sort by **Event Date**. Identify the January 1 Open Enrollment row (check if its status is **On Hold**, **Rescinded**, or **Canceled**) and every row with an earlier **Event Date** still sitting in **In Progress** or awaiting a business process step.
2.  **Decide whether the earlier-dated benefit event is legitimate.**
    -   **Created in error by an unneeded job-change trigger:** Many tenants accidentally generate benefit events on non-qualifying job transfers because **Restricted by Reason** is blank on **Maintain Enrollment Event Types** or **Allowed Benefit Plan Changes** is set to **Can select any plan** instead of **Only on Eligibility Change** on **Edit Enrollment Event Rule**. If the earlier benefit event should never have existed, cancel or [rescind the business process](https://kiweely.com/guides/workday-business-process-rescind-cancel-correct) from its **Overall Process** link (required security: **Process: Open Enrollment** or **Manage: Benefits for Organizations** in the **Benefits** functional area, plus business process security).
    -   **Legitimate qualifying event (such as birth, marriage, or benefit-group transfer):** Complete the earlier-dated event first. Either have the employee submit their 2026 elections, enter them on the worker’s behalf as a Benefits Partner, or close it out via **Finalize Open Benefit Event Elections**.
3.  **Verify the recreated January 1 Open Enrollment event.** Immediately after the earlier-dated event completes or cancels, refresh **Benefit Election History**. Confirm that Workday rescinded the held Open Enrollment row and created a new Open Enrollment row for January 1 with an updated **Submit By** date.
4.  **Re-add workers whose Benefit Group changed mid-window.** If a backdated transfer moved an employee *into* an eligible Benefit Group after Open Enrollment started (or after the main window closed), inspect **Eligible Workers with no Open Enrollment**. Then open **Open Enrollment Status Report > View Details > Related Actions > Open Enrollment > Add Workers**, select the worker, and specify an **Open Until** date so the event does not immediately close on them (see [how to reopen Workday Open Enrollment for one employee](https://kiweely.com/guides/workday-reopen-open-enrollment-single-worker)).
5.  **Confirm downstream carrier impact.** Run **View Current Benefit Elections** as of both today and January 1. Once Open Enrollment is closed and finalized, confirm the worker and all covered dependents appear accurately before your [Cloud Connect for Benefits 834 carrier feed](https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors) runs.

## How to Stop Routine Q4 Changes From Putting Open Enrollment On Hold

You cannot (and should not) stop Coordination of Events when a worker genuinely changes Benefit Groups or gains/loses plan eligibility in November. However, you *can* stop low-impact fourth-quarter updates, such as standalone beneficiary edits or minor non-overlapping changes, from putting thousands of January 1 Open Enrollment events **On Hold**:

-   **Configure `Do Not Reprocess` and `Do Not Reprocess Future Events` selectively.** Using **Edit Open Enrollment Event Type** and **Edit Benefit Event Type** (secured by **Set Up: Benefits** in the **Benefits** functional area):
    -   Selecting **Do Not Reprocess Future Events** on an earlier benefit event type (for example, `Beneficiary Change` dated December 20) prevents Workday from placing a later-dated event (such as January 1 Open Enrollment) **On Hold**, provided there is no gain or loss in benefit eligibility.
    -   Selecting **Do Not Reprocess** on the Open Enrollment event type prevents earlier non-eligibility events from placing Open Enrollment **On Hold** and rescinding submitted elections.
-   **Tighten `Change Job` benefit event triggers before November.** Open **Maintain Enrollment Event Types** and **Edit Enrollment Event Rule**. Verify that routine supervisory or cost-center moves during fourth-quarter reorganizations do not spawn unnecessary benefit enrollment events that collide with Open Enrollment.
-   **Set a realistic `Days to Enroll` under Coordination of Events.** On **Edit Open Enrollment Event Type**, review **Days to Enroll** in the **Coordination of Events** section. If Coordination of Events recreates a worker’s Open Enrollment event *outside* the main enrollment window, the worker receives only the number of calendar days configured in that field to submit their recreated elections.

## Audit stuck enrollment events and build benefit reports with Kiweely Vine

When dozens of workers hit **On Hold** mid-window during a fourth-quarter reorganization, **[Kiweely Vine](https://kiweely.com/download)** inspects live **Benefit Election History**, **Maintain Enrollment Event Types** and stalled business processes in your connected tenant, and builds custom audit reports and calculated fields from a plain request — in recorded sessions in Kiweely’s own Workday Development tenant, Vine built and checked a custom organization report in 38 minutes (3 of 3 checks passed) and a multi-condition benefits-review `Evaluate Expression` calculated field in 50 minutes 18 seconds (6 acceptance checks passed, 0 failed, 2 not run). Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month.

[Download Kiweely Vine free](https://kiweely.com/download) · [Watch the benefits calculated-field build (10 min)](https://www.youtube.com/watch?v=aHnNpdrkTdA)

## Frequently asked questions

### Why did an employee's Open Enrollment task vanish from My Tasks after HR entered a November job change?

Because Open Enrollment uses a future event date such as January 1, any November or December benefit event with overlapping coverage types or an eligibility change triggers Coordination of Events. Workday puts the January 1 Open Enrollment event On Hold until the earlier November benefit event is completed, canceled, or rescinded.

### What happens to elections an employee already saved or submitted before Open Enrollment went On Hold?

Once the earlier-dated blocking benefit event completes, Workday rescinds or cancels the On Hold Open Enrollment event and creates a replacement Open Enrollment event for that worker. Workday preserves prior completed elections where eligibility still applies, but unsubmitted In Progress changes or newly eligible plans require the worker or Benefits Partner to review and submit the recreated event.

### Does checking Do Not Reprocess stop every backdated change from putting Open Enrollment On Hold?

No. Selecting Do Not Reprocess on the Open Enrollment event type or Do Not Reprocess Future Events on an earlier benefit event type only bypasses Coordination of Events when coverage types overlap without an eligibility change. Workday always reprocesses future events when a worker gains or loses coverage eligibility or changes Benefit Groups.

### What happens if a manager submits a staffing or life event effective on the exact same date as Open Enrollment?

Unlike regular life and staffing events that merge into a single hybrid event on the same day, Workday never consolidates another benefit event with Open Enrollment. If Open Enrollment already exists on January 1, non-Open Enrollment benefit events must use a different event date, and if a life event existed on January 1 before Open Enrollment started, Workday cancels or rescinds that life event.

## Sources checked

-   [Concept: Coordination of Benefits Enrollment Events](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/enrollment-events-and-rules/dan1370797033818.html)
-   [Create Enrollment Events](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/enrollment-events-and-rules/dan1370797378594.html)
-   [Concept: Multiple Benefit Events on the Same Day](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/enrollment-events-and-rules/dan1370797033268.html)
-   [Steps: Manage Open Enrollment](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/open-enrollment/dan1370797548364.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How to Reopen Workday Open Enrollment for One Employee After the Window Closes To reopen Workday Open Enrollment for one employee after the window closes, enable Enable Reopen of Open Enrollment on the event type, then use Reopen Enrollment on that worker’s closed or finalized event, or Add Workers with an Open Until date if they never had an event.](https://kiweely.com/guides/workday-reopen-open-enrollment-single-worker)
-   [### How to Troubleshoot Workday Cloud Connect for Benefits (CCB) and Missing Dependents on 834 Feeds Missing dependents on a Workday Cloud Connect for Benefits ANSI X12 834 file usually mean absent elections, Integration System User security gaps, or drops from maps, field overrides, or launch parameters. Prove the layer with View Current Benefit Elections and the CCB Debug Service.](https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors)
-   [### What does rescinded mean in Workday? Rescind vs cancel vs correct, and when each applies Rescinded means Workday reversed a business process that had already passed its Completion step and restored the data to how it was before. Cancel stops one still in progress; Correct fixes the event’s details in place.](https://kiweely.com/guides/workday-business-process-rescind-cancel-correct)
-   [### Workday Awaiting Action: who is the step waiting on, and how do you move it? Awaiting Action means a step is waiting for someone to act, and a day or more is normal. Open Business Process > Full Process Record to see who, then have them finish it in My Tasks, or reassign, delegate or manually advance the step.](https://kiweely.com/guides/business-process-awaiting-action)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [How to Configure or Opt Out of the Modernized Workday Worker Profile and Private Tab](https://kiweely.com/guides/workday-worker-profile-header-private-public-tabs)
-   [How Future-Dated Dependents and ‘View Dependent As Of’ Work in Workday Benefits](https://kiweely.com/guides/workday-dependent-effective-dating-future-dependents)
-   [How Workday Data Cloud Zero-Copy Sharing Works with Snowflake, Databricks, and BigQuery](https://kiweely.com/guides/workday-data-cloud-zero-copy-snowflake-databricks)
-   [Workday Platform Consumption Console: what each page shows, when usage updates and what the alerts do](https://kiweely.com/guides/workday-platform-consumption-console)
-   [Workday Tickets for a Small HRIS Team: Workday Help, Jira or ServiceNow, and How to Triage the Queue](https://kiweely.com/guides/workday-hris-ticketing-help-jira-servicenow)
-   [What Workday AMS Costs in 2026: Hourly Rates, Retainers and What They Cover](https://kiweely.com/guides/workday-ams-cost)
-   [Hire Another Workday HRIS Analyst or Add an AI Team? The Monthly Cost Compared for 2026](https://kiweely.com/guides/hris-analyst-or-ai-team-cost)
-   [Workday Configuration Catalog packages: filter, test, then migrate](https://kiweely.com/guides/workday-configuration-catalog-packages)

### From the blog on More Workday guides

[All posts](https://kiweely.com/blog)

-   [Why Do Workday Implementations Run Late or Over Budget? Each Cause, and How to Prevent It](https://kiweely.com/blog/workday-implementation-late-over-budget)
-   [How much do Workday partners and consultants charge?](https://kiweely.com/blog/workday-consultant-partner-rates-sow-pricing)
-   [Is there a Workday plugin or connector for ChatGPT?](https://kiweely.com/blog/workday-plugin-for-chatgpt)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
