Burlington Workday Login Not Working? Fix It in 7 Steps

Step 1: Verify the URL

Takeaway	Detail
Use the direct tenant URL, not the generic Workday page	Burlington’s portal is at wd5.myworkday.com/burlington — the public myworkday.com sign-in won’t list Burlington, so bookmark the exact address.
Test in an incognito window first to isolate browser cache	A private session bypasses corrupted cookies and cached scripts, resolving most “login won’t load” cases in under a minute.
Check the vendor status page before assuming an outage	Workday posts scheduled maintenance windows (typically 2-4 hours overnight), so a quick status check saves you from resetting credentials during a known downtime.
Reset credentials only after verifying Caps Lock and account lockout	“Invalid Credentials” is usually a keyboard or session issue; lockouts auto-clear after a short wait, so hold off before calling HR.
Escalate to Burlington HR helpdesk, not the store manager, for persistent failures	HR has Workday admin console access to force a password reset or unlock your account — the store manager cannot.

Most “Workday is down” complaints are actually local issues: a stale browser cache, a locked account, or a session that expired while you were away. By following these seven steps in order, you’ll eliminate each variable until the login either works or you have a ticket number to hand to payroll.

Step 2: Isolate Browser

The fastest test for a Burlington Workday login failure is the incognito window, and it costs you about ten seconds. Open a private browsing session in whatever browser you normally use, navigate to the Burlington tenant URL, and attempt the login. If you get in, the problem is stored browser data — cache, cookies, or session tokens — not your credentials and not Workday's servers. If you still fail, you have eliminated the browser as a variable and can move to the next step with confidence.

Extensions are a quieter failure mode. Script blockers like uBlock Origin and privacy tools like Privacy Badger can interfere with the redirect chain that Workday's SSO relies on, and corporate VPN extensions can route you through a proxy that rejects the authentication handshake. One r/sysadmin thread from June 2026 described a redirect loop caused entirely by a cookie-cleaning extension that was purging the session token mid-authentication. If you use any extension that touches cookies, redirects, or scripts, disable it for the Workday domain or test in a browser profile with extensions off entirely.

If the incognito test passes, the decision rule is simple: clear cookies for the Workday and IdP domains specifically, then retry in your normal window. If the incognito test fails, do not keep clearing cache and retrying — that is the loop that wastes an hour. Instead, switch to a second browser entirely. Chrome, Edge, Firefox, and Safari all handle SSO cookies differently, and a login that works in one but not another points to browser configuration, not a Workday problem. A field report on a retail IT thread noted that Firefox often succeeds when Chrome fails on the same machine because of how each browser partitions third-party cookies by default.

One edge case deserves attention before you escalate: if you are on a Burlington store computer, the browser settings may be locked down by IT policy. Do not attempt to change proxy settings, disable extensions, or modify security policies on a managed device — you will likely trigger a compliance alert and lock yourself out further. Use the official IT support path for store hardware. For your personal device, the incognito test plus targeted cookie clearing resolves the majority of browser-related failures, and the whole sequence takes under five minutes. If you have done both and still cannot authenticate, the issue is not the browser, and you should proceed to the outage check in the next step.

Step 3: Check Outages

Workday’s official sign-in page does not list Burlington as a public tenant, and its fallback directive is to “contact your administrator” when you cannot find your company’s login. That instruction is also your best outage-confirmation path: your store manager or HR contact receives vendor notices directly, so a single phone call or Slack message to them resolves the “is it down or is it me” question faster than any status page refresh. The administrator sees the same maintenance calendar you do, but they also see tenant-specific advisories that never reach the public status page.

Field threads on r/sysadmin repeatedly describe a different failure mode: “Workday is down” turns out to be a local network problem misattributed to the vendor. DNS resolution fails, a firewall rule blocks the subdomain, or a VPN tunnel drops mid-authentication — and the user blames Workday because the page never loads. The ten-second test is to load any other website, ideally a different domain entirely, on the same device and network. If other sites load fine, the issue is specific to the Workday domain, which points back to DNS or proxy rules rather than a vendor outage.

Scheduled maintenance windows typically run two to four hours and land overnight, which is why most associates never see them. If you are trying to clock in during a window, your manager should have received a notice — that is standard practice for retail operations with shift-based workforces. The decision rule is straightforward: check the vendor status page first, then test whether other sites load, then switch networks if you are on a store connection, and only then move to credential troubleshooting. Skipping the network test is the most common mistake, because it sends you down a password-reset path that can lock an otherwise healthy account.

One caveat: vendor status pages are accurate for planned maintenance, but they lag on unplanned incidents. If the status page shows green and other sites load fine, the problem is almost certainly local or account-level — proceed to the browser and credential steps with that assumption. If you are on a store network and the hotspot test passes, do not keep retrying the store connection; escalate the network block to your manager or IT contact with the specific domain name in hand.

Step 4: Reset Credentials

Most Burlington associates who hit "Invalid Credentials" burn twenty minutes resetting a password they never needed to change. The error means the username or password is incorrect, and the two most common causes are Caps Lock and Num Lock, not a forgotten password. Check both before you touch the reset flow. Workday's own guidance on the error is blunt: verify the credentials before attempting a reset, because a false credential failure sends you down a path that can lock the account entirely.

The "Forgot Password" flow itself has a hidden dependency that trips up more people than the password does. Workday typically requires email or SMS verification to send the reset link, and that verification goes to the recovery method on file. If your primary email is a Burlington corporate address that you can no longer reach — you're a former employee, you left the company, or your mailbox was deprovisioned — the reset email will never arrive. One practitioner thread describes a user whose recovery email was an old personal address they had abandoned years ago; they spent three days assuming Workday was broken before HR updated the contact method. The decision rule: if no reset email arrives within ten minutes, do not keep clicking "resend." Check spam and junk folders first, then confirm the email on file is actually reachable. If it is not, you must contact HR to update the recovery method before the reset flow can work at all.

There is also a distinction that confuses people who work with Burlington's vendor systems. Burlington Stores' Gateway is a separate portal for EDI (electronic data interchange) partners, not the employee Workday login. Gateway credentials will not authenticate against Workday, and trying them repeatedly is a fast way to trigger an account lockout. If you are a vendor or partner, you are on the wrong system entirely; if you are an employee, make sure you are not entering a Gateway password out of habit.

The "Account Locked" edge case is where most people make the situation worse. Do not keep retrying during that window — every additional attempt extends the lockout timer. The correct sequence is: check keyboard locks, use Forgot Password, wait ten minutes for the email, and if nothing arrives, contact HR to verify the recovery method. That order eliminates the false credential failure before you trigger a lockout, and it gets you to a human with the authority to unlock the account instead of a password reset loop that never resolves.

One more thing worth knowing: Workday login sessions expire after a period of inactivity, and the "Session Expired" error does not require a password reset. It requires a full re-login. On a trusted personal device, the "Remember Me" checkbox reduces how often you hit that wall, but it does not change the underlying session timeout. If you see "Session Expired," close the tab, reopen the tenant URL, and sign in again — do not treat it as a credential problem.

Your next action today: before you attempt any reset, verify the keyboard locks, then trigger the Forgot Password flow and set a ten-minute timer. If no email arrives, call Burlington's HR or payroll line directly — the number is on your pay stub or the associate portal — and ask them to confirm the recovery email on file. That single call resolves more lockouts than any amount of retrying.

Step 5: Check Account State

Your account state is the variable most people skip, and it explains more lockouts than any browser or network issue. If you are actively employed and clocking in normally, skip this step and go straight to Step 6. But if you are on leave, recently terminated, or a rehire, no amount of password resets will help — the account itself is the problem, and the fix lives with HR, not with your keyboard.

Burlington’s employee resources page directs payroll and login questions for both current and former employees to the Burlington Payroll department at 609-387-7800. That number is the escalation point when your account state is the suspected cause. A terminated employee typically retains Workday access for a grace period of one to two weeks to pull final paystubs, per threads in r/humanresources. If you are locked out sooner than that, the account was likely deactivated early — a payroll call resolves it faster than any self-service flow. Do not burn an hour retrying credentials when the account flag is the actual blocker.

Role changes are a quieter failure mode. A store associate promoted to manager, or any transfer between positions, can temporarily disable access during the transition window. The Workday admin console often holds the account in a pending state until the new role is fully provisioned. Practitioners report that waiting 24 hours before aggressive troubleshooting is the correct move here; aggressive resets during that window can actually compound the problem by triggering additional security flags. If you changed roles in the last day, wait, then test once. If it still fails, call HR — they can see the provisioning status you cannot.

Rehires hit a different trap. Your old account is typically archived, and Burlington creates a new Workday profile tied to your new employee ID. Using your old credentials or your old employee ID will fail every time. The correct path is the Forgot Password flow with the new employee ID only — never your old one. If you do not know your new ID, that is an HR question, not a login question. The same logic applies to first-time access for income verification through The Work Number: that is a separate system with its own enrollment steps, and confusing it with Workday login is a common detour that wastes time.

One more distinction worth naming: Workday’s official sign-in page uses a Workday Digital ID account, which is separate from the tenant-specific login Burlington employees use. If you are on the generic Workday portal and trying to authenticate there, you are in the wrong system entirely — as noted above, the tenant URL is the only entry point that matters. The Digital ID flow is for Workday’s own products, not for Burlington’s HCM instance.

Decision rule: if you are active and employed, proceed to Step 6. If you are on leave, terminated, or rehired, call 609-387-7800 before any further troubleshooting. Your next action today: check your employment status against that rule, and if you fall into the leave, terminated, or rehire bucket, make the call now — it is a five-minute conversation that saves you the entire reset loop.

Step 6: Apply the Decision Rule

The fastest way to resolve a Burlington Workday lockout is to stop troubleshooting and check your employment status first. That single decision determines whether you spend five minutes clearing cookies or five minutes on the phone with payroll. Most articles tell you to clear cache and retry; field threads describe associates burning an hour on browser fixes when their account was deactivated a week earlier.

Consider three concrete paths. Option A: Sarah, a store associate, hits "Session Expired" on her work computer mid-shift. She opens an incognito window, logs in successfully, then clears cookies for the Workday domain only. Total time: under five minutes, zero cost, no IT ticket. This is the most common resolution path, and it aligns with what one r/sysadmin thread notes: "Session Expired" is the most frequent Workday complaint that isn't a real problem, and a full re-login resolves it essentially every time.

He checks Caps Lock, confirms it's off, then triggers the Forgot Password flow. The reset email arrives in about two minutes, he sets a new password, and he's back in within ten minutes total. The key detail here is that Marcus did not call IT or submit a ticket — the self-service reset worked because his recovery email was still active and his account was in good standing.

Dana was terminated last week and needs her final paystub. Her Workday account is deactivated, and the Forgot Password flow fails because her corporate email is already dead. No amount of cache clearing, incognito testing, or password reset attempts will help — the account simply no longer exists in an active state. As detailed in the Step 5: Check Account State section, she calls Burlington Payroll, verifies her identity, and receives her paystub. Cost: one phone call, no login required.

The decision rule is straightforward. If you are actively employed and the browser is the issue, fix it locally with the incognito test and targeted cookie clearing. If you are actively employed and credentials are the issue, reset them through the self-service flow. If you are inactive, terminated, or on leave, skip Workday entirely and call payroll directly. That last path is the one most articles omit, and it's the one that saves the most time.

One edge case worth noting: account lockout after multiple failed attempts. According to Workday's official documentation, accounts lock after five failed login attempts, and the lockout auto-releases within 15 to 30 minutes. If you've been hammering the password field, wait out the window before trying again — resetting your password while locked out can extend the lockout or create a second credential problem. If you changed roles recently, wait a day before testing; role changes can propagate slowly through the identity provider.

Your next action today: before touching another setting, confirm your employment status. If you're active, run the incognito test. If you're not, call the payroll number on your last pay stub and skip the login screen entirely.

What to do next

After working through the seven steps, you should have isolated the cause of your Burlington Workday login failure. If the issue persists, the next actions are about confirming the official path and escalating through the proper enterprise channels. Set a calendar reminder to test your login again tomorrow at 9 AM — if it passes, the issue was a temporary provisioning delay; if it fails, call 609-387-7800 today to confirm your account state and get a definitive answer from payroll.

Step	Action	Why it matters
1	Verify the exact tenant URL by checking your Burlington onboarding email or internal HR portal for the direct link (e.g., wd5.myworkday.com/burlington).	Workday does not list Burlington as a public tenant; using the correct subdomain prevents redirect errors and phishing risks.
2	Test your login in a private/incognito browser window with cookies and cache disabled.	Isolates browser-stored data corruption, which is a common cause of repeated login failures.
3	Check Workday’s official status page (status.workday.com) or the vendor maintenance notice for scheduled outages before retrying.	Confirms whether the issue is server-side and saves time troubleshooting your own account.
4	Use the “Forgot Password” flow only if you can receive email or SMS at the recovery method on file; otherwise, contact Burlington HR to update it first.	Prevents lockouts and ensures the reset link reaches a valid inbox, especially if your corporate email is unreachable.
5	If you are a Burlington employee, confirm you are using the core Workday HCM portal, not the separate Adaptive Planning login.	Avoids confusion between distinct Workday products and reduces time spent on the wrong sign-in page.
6	Escalate to your Burlington IT helpdesk or HR administrator with a screenshot of the error and the exact time it occurred.	Provides the necessary details for enterprise support to trace the issue and verify your account status.
7	Set a calendar reminder to test your login again tomorrow at 9 AM, and if it still fails, call Burlington Payroll at 609-387-7800 to confirm your account state.	Confirms whether the issue was a temporary role-provisioning delay or a persistent account problem that requires HR intervention.

If you are actively employed, the incognito test and credential reset should have resolved the issue. If you are on leave, terminated, or a rehire, the payroll line is your definitive next step — call today rather than retrying the login screen. For everyone else, schedule that 9 AM test tomorrow; if it passes, you are done, and if it fails, you have a ticket number and a clear escalation path.

=======

6Escalate to your Burlington IT helpdesk or HR administrator with a screenshot of the error and the exact time it occurred.Provides the necessary details for enterprise support to trace the issue and verify your account status.7Set a calendar reminder to test your login again tomorrow at 9 AM, and if it still fails, call Burlington Payroll at 609-387-7800 to confirm your account state.Confirms whether the issue was a temporary role-provisioning delay or a persistent account problem that requires HR intervention.

Also worth reading: Burlington Workday Login 7 Critical Updates Employees Need to Know for 2024 · How to Fix Slack Notifications Not Working on MacBook A 7-Step Technical Solution · Workday Ensign Login Security Features Behind the Two-Factor Authentication Process in 2024 · 7 Key Security Features Every MGM Employee Should Know About Their Workday Login in 2024

Sources: workday, burlington, myworkday, eathealthy365, ibacana