Back to Washington Unemployment

Connor Gallagher

ESD SAW account bug cant submit unemployment application - anyone else hit this?

Two weeks into what should have been a straightforward process and I'm completely stuck. Got laid off from my warehouse job mid-January, figured I'd get the unemployment application knocked out the same day. Went through the whole SecureAccess Washington setup, created my SAW account, linked it to the ESD portal like the instructions said - and then hit a wall. Every time I try to submit the actual unemployment application, nothing happens. Click the submit button and it just... sits there. No error message, no confirmation, no spinning wheel, absolutely nothing. The page doesn't reload. The application doesn't go anywhere. I've tried this on Chrome, Firefox, even dug out an old laptop to test on Edge. Same result every time. Cleared cache, cleared cookies, disabled extensions, tried incognito mode. The application fills out fine - all my employer info, my separation reason, everything - but that final submit button is completely dead. I'm now two weeks behind on filing and genuinely panicking because I know the clock is ticking on when my benefit year starts and whether I'll qualify for the full amount. Anyone run into this specific thing where the SAW account seems connected but the ESD application submit function is totally broken? Is this a known bug? Do I need to call someone to get it manually submitted or override something on their end? Really need help figuring out the next step here.

Day 4 of my own adjudication nightmare so I feel this deeply. The SAW-to-ESD connection has been glitchy for months, you're not imagining it. The most common culprit I've seen people report is a partial account linking issue - your SAW login works but the ESD system thinks your identity verification isn't fully completed on their backend. The submit button silently fails because the system won't accept an application it considers 'unverified.' What you can try: log completely out of both SAW and ESD, go back to secure.esd.wa.gov directly (not through SAW), and look for an option to re-verify your account linkage. Sometimes there's a pending step that never sent you a notification.

0 coins

Tried the re-verify route when I was at week one of my claim and the link looked fine on both ends. Turned out the problem was actually that my browser was blocking a redirect that happens between SAW and ESD during submission. Disabling tracking protection in Firefox fixed it for me instantly.

0 coins

the redirect block thing is real, happened to my roommate. but also check if you have any kind of VPN running, that can interfere with the SAW handoff to ESD in a really specific way that looks exactly like a dead submit button

0 coins

Just got my determination letter yesterday after a 5-week wait so I'm finally on the other side of this. When I first tried submitting I hit something similar and spent two full days troubleshooting browser stuff before I realized the actual fix was way simpler - there's a session timeout that happens on the ESD application if you've been filling it out for more than roughly 20-25 minutes. The form looks totally fine and lets you keep typing but the session underneath has expired. When you hit submit it goes nowhere because the session token is dead. Try filling out the whole application in one shot as fast as you can and submit immediately, don't stop to look things up mid-form.

0 coins

Hadn't even considered the session timeout angle - I definitely took breaks while filling it out. Going to attempt the whole thing start to finish without stopping and see if that's what's killing it. How long did the full application take you when you rushed through it?

0 coins

session timeout was my issue too, got past week 2 before I figured this out. the annoying part is they don't warn you at all, the form just silently dies

0 coins

20 minutes seems really short for a session. some people have complicated work histories and need time to gather all their employer info and dates

0 coins

Three weeks into my own claim process when I ran into the ESD phone contact nightmare trying to sort out a similar application issue. After calling the main ESD line six times and getting disconnected or hitting the 'we cannot take your call' message, someone in a Facebook group for Washington claimants pointed me toward a service called Claimyr. The idea is it navigates the ESD phone queue for you and calls you back when an actual agent picks up - so you're not sitting on hold for hours. I was skeptical but I was desperate. Used it, got connected to an ESD agent within about 90 minutes, and the agent was able to flag my account for a manual application review. Site is claimyr.com and there's a video showing how it works at https://youtu.be/7DieNd3C7zQ if you want to see before trying it.

0 coins

Bookmarking this because if the browser fixes don't work I'm going to need to talk to an actual human at ESD. The phone situation has been brutal every time I've tried - does Claimyr work for general application submission issues or is it mainly for claim status stuff?

0 coins

got connected through it last month when my adjudication stalled. the agent I reached could actually see my account and do things, not just read me the same info I could see online

0 coins

wish I'd known about this when I was fighting my week 3 access issue. spent literally an entire workday calling and redialing

0 coins

Currently at the stage where I'm waiting on my first weekly claim certification so this is fresh for me. I had a different version of the submit problem - my button was grayed out rather than unresponsive. Turned out I'd skipped a question that looked optional but wasn't - it was about union membership and I'd left it blank because I assumed it was only for union workers. ESD's required fields aren't all marked with the usual asterisk. Worth scrolling through every single question to make sure nothing got left blank even if it looked like it didn't apply to you.

0 coins

Missing required fields that aren't marked was exactly what tripped me up at week one too. The union question and also the 'are you available for all shifts' question both caught me because they look like they're for specific situations only

0 coins

Going back through the form with fresh eyes on every question, not just the starred ones. This is a really good catch - the form design is genuinely confusing about what's mandatory.

0 coins

esd forms are notoriously bad about this, same issue shows up in the weekly claim certifications too where certain answers unlock more required fields that arent obvious

0 coins

Received my approval notice last week so I can share what finally worked for me after a nearly identical submit failure. I used to think the SAW account just needed to exist and be linked - turns out the ESD system actually checks whether your SAW account has completed what they call 'identity proofing' at the medium assurance level, not just the basic one. If you created your SAW account quickly without uploading any identity documents, you might be stuck at basic assurance and the application submission requires medium. Go into your SAW account settings, look for the assurance level, and if it shows basic you'll need to complete additional verification steps before ESD will accept the submission.

0 coins

Went back and checked my SAW account settings when I was at this exact problem point and found it sitting at basic assurance. Upgraded it and the submit button worked on the first try. This is probably the most common real fix that doesn't get mentioned in the basic troubleshooting guides.

0 coins

I didn't even know assurance levels were a thing until reading this, the SAW setup process really should explain this better

0 coins

The identity proofing thing tripped up a lot of people I know. ESD should put a check for this earlier in the application flow instead of letting you complete the whole form and then silently fail at submission

0 coins

Halfway through my appeal process for a separation dispute and I remember the application submit issue clearly. Mine was a weird one - the application was actually submitting successfully but I wasn't getting any confirmation screen because of an issue with how my browser handled the redirect to the confirmation page. I thought it was failing when it had actually gone through twice. Logged into my ESD account dashboard a day later and found two pending applications. If you haven't already, check your ESD dashboard directly after trying to submit to see if anything is sitting there in a pending state before you try again.

0 coins

Checking the dashboard now - never thought the application might actually be going through without showing me a confirmation. That would explain a lot honestly.

0 coins

duplicate applications are a real headache, ESD has to manually merge or dismiss the extra one and that can apparently add time to processing

0 coins

Got my first weekly claim payment pending so things are moving for me finally. What helped me after I read about similar issues online: calling the ESD tech support line specifically, not the main claims line. There's a separate technical support number for SAW and ESD portal issues and those agents actually know the system backend. They can see error logs tied to your account that regular claims agents can't access. Also, separately - I tried Claimyr to reach an ESD tech agent when the regular lines were impossible, and it actually worked. Got through to someone who could see a specific error flag on my account that was preventing submission. The fix took them about 3 minutes once they found the flag.

0 coins

Spent my first week calling the main line and getting nowhere before someone told me about the separate tech support path. The agents there actually troubleshoot instead of just telling you to clear your cache

0 coins

Didn't know there was a separate tech support line - every time I've called ESD I've just been hitting the main queue. Where do you find that number, is it on the ESD website somewhere specific?

0 coins

Found the tech support contact info on the ESD portal help page - going to try this route since it sounds more targeted than the main claims line for a system issue like mine.

0 coins

My benefit year just started last week so I went through the whole application process recently. The thing that caused my submit failure was something embarrassingly simple - I was using autofill for my Social Security number and it was putting a space at the end. The SSN field looked correct on screen but had an invisible trailing character that failed validation silently on submission. Turned out clearing that specific field and manually retyping just my SSN fixed it. Worth checking any autofilled fields carefully.

0 coins

Autofill causing invisible character problems in government forms is way more common than people realize. Spent three days trying to submit a different government form before figuring out the same thing.

0 coins

This is a really good one to check. The ESD form has a few fields that seem to reject autofill entries even when they look right on screen, SSN and routing number for direct deposit were both issues for me

0 coins

Just got to the job search log requirement phase of my claim so the application part is behind me. I want to flag something that confused me for a while - I used to think that if the SAW account was created and showed as 'active' that meant everything was connected properly to ESD. The active status in SAW just means the SAW account exists, it doesn't confirm the ESD benefit account is properly provisioned on their side. Sometimes ESD has to manually create the benefit account after you apply, and if that step fails or stalls, you can have a perfect SAW account and still not be able to submit because there's nothing on the ESD backend to receive your application. If you've been going in circles on the technical fixes, an ESD agent can check whether your benefit account was actually created.

0 coins

This happened to someone I know who was trying to file - everything looked right from the user side but ESD's backend hadn't created the benefit account record. Agent fixed it in one call and the application went through immediately after.

0 coins

The SAW active status being different from ESD account provisioning is a distinction that should absolutely be in the ESD FAQ but isn't. Really useful to know.

0 coins

so the UI system can look working from your side but be broken on their end with no error message at all? that's genuinely terrible design

0 coins

Filing my third week of weekly claims now. When I first hit the submit bug I went down a long rabbit hole of browser troubleshooting but the fix ended up being that my ESD account had a hold flag from an identity verification mismatch - my name on the SAW account had a middle initial and my ESD information didn't, and their system flagged it as a potential mismatch even though it was obviously the same person. ESD can clear that flag manually but you do need to call them. The name has to match exactly across SAW and ESD, including whether you use a middle name, suffix, or any abbreviation.

0 coins

Name mismatch flags are super common and ESD doesn't tell you that's the problem, you just get a silent submission failure. Middle initials, hyphenated last names, and suffixes are the usual culprits.

0 coins

Going to double check that my name is completely identical across both systems - I may have put my full middle name in one place and just an initial in another without thinking about it.

0 coins

At week six now and looking back, the SAW to ESD connection issues were the most frustrating part of my whole claim experience. For anyone hitting the submit bug: the fastest path I found was using ESD's online message portal to send a written description of the technical issue with screenshots attached. I got a response within 48 hours and they had someone call me to fix the backend issue. It doesn't get talked about much but the message portal actually has better response rates than calling, at least for technical account issues.

0 coins

Sent a message through the portal when I was stuck at week two and got a callback within a day and a half. Way better than what I experienced trying to call.

0 coins

didn't know you could attach screenshots to the ESD message system, that changes things. been writing out long descriptions of technical problems without any visual reference

0 coins

The portal message route is legitimately underrated. The agents who handle written tickets seem to have more access to backend account tools than the standard call center agents.

0 coins

Reached the determination letter stage finally after a rough start that included the exact submit bug you're describing. What eventually got things moving for me was combining approaches - I sent the portal message AND used Claimyr to get through on the phone at the same time. The phone agent I reached through Claimyr could see the portal ticket I'd opened and was able to escalate it while I had them on the line. Having both channels open simultaneously sped things up significantly. The agent said the submit failure on my account was caused by a corrupted session token that persisted in their system even after I cleared my browser - something they could only fix on the backend.

0 coins

Running the portal message and phone call simultaneously to let the agent reference the existing ticket is actually a smart move - gave the agent something to look at and work from instead of starting from scratch.

0 coins

The corrupted session token persisting on ESD's backend is a real thing apparently, not just a browser issue. Good to know that's something they can actually clear when you get through to the right person.

0 coins

Just got notified my job search activities are under review which is a whole other nightmare, but I remember the application phase well. One thing nobody mentioned: if you're on a mobile device or tablet, the ESD application submit button just doesn't work reliably. The ESD portal is not properly optimized for mobile and the submit function specifically has known issues on mobile browsers. If you've been trying on a phone, switch to a full desktop or laptop browser and that alone might solve it.

0 coins

Spent two days frustrated trying to submit from my phone before switching to my desktop and it worked immediately. This should honestly be in big red letters on the application page.

0 coins

the ESD portal being basically unusable on mobile in 2025 is wild to me. everything should work on a phone at this point.

0 coins

Even on desktop some people have issues with smaller screen resolutions - full-screen the browser window and make sure you're at 100% zoom, not zoomed in or out at all

0 coins

Got through the application phase about a month ago and remember it being miserable. The piece that finally clicked for me: I used to assume that because I could log in and navigate the ESD portal just fine, my account was in good shape. But being able to log in and browse has nothing to do with whether your account has what they call 'submission permissions' active. ESD has to flip a flag on new accounts before they'll accept an application, and that flag is usually set automatically but occasionally doesn't trigger. An agent can manually set it in about two seconds. The whole frontend works - you can fill out everything - but submission just silently dies until that flag is set.

0 coins

That submission permissions flag being separate from login access is infuriating because there's no way to even check it yourself. Everything looks fine until the moment you need it to actually do something.

0 coins

This matches what happened to my neighbor - called ESD, agent said something about enabling submission on the account, and it worked minutes later. No explanation of why it wasn't set in the first place.

0 coins

Week one of weekly certifications here, still early in my claim. When I went through this same issue, the ESD rep on the phone told me something interesting - they occasionally have to push a system update that temporarily disables new application submissions for a window of a few hours, and if you try during that window you get a silent failure with no notification. They're supposed to post system maintenance alerts but apparently don't always. She suggested always checking the ESD system status page before attempting to submit and also not trying to submit on Monday mornings which is apparently when most maintenance windows happen.

0 coins

Maintenance window timing was the culprit for me - tried to submit Sunday night during what turned out to be a maintenance period. Tried again Tuesday morning and it went straight through.

0 coins

This is good practical advice. I've been trying to submit at all hours without checking system status first. Going to look for the ESD status page and check it before my next attempt.

0 coins

The lack of notification during maintenance windows is a known complaint and ESD has been called out about it before. For something this critical they really should have a banner on the application page.

0 coins

Waiting on my adjudication decision currently and the application submit issue feels like a distant memory at this point. Something worth trying if everything else fails: log out of both ESD and SAW completely, then go to SAW first and do what's called a 'fresh authorization' by going to Manage Applications in your SAW account and removing and re-adding the ESD connection. This forces a new authorization token to be issued. I used to think the SAW-ESD connection once linked stayed good forever without maintenance. The connection actually has a token that can expire or corrupt, and re-authorizing it issues a fresh one that can clear the submission block.

0 coins

Re-authorizing the SAW to ESD connection solved it for me too - removing and re-adding the ESD application from the SAW Manage Applications screen is something I'd never have thought to try without reading about it here.

0 coins

the authorization token expiring is not documented anywhere I could find. ESD should really have a checklist somewhere that includes this step for submit failures.

0 coins

Went through the re-authorization process when I was stuck at this same point and it was the fix. Takes about five minutes and doesn't affect any of your application data.

0 coins

About to submit my fourth weekly claim certification so the initial application is behind me. For people dealing with this: the ESD office in Tacoma actually has walk-in technical assistance for SAW and portal issues on certain days. I know not everyone can get there but if you're near a WorkSource office, calling them directly about a portal technical issue is different from calling the main ESD claims line - WorkSource staff sometimes have direct access to ESD technical staff and can escalate faster.

0 coins

WorkSource being a faster path to technical ESD staff is a genuinely useful piece of information. The main ESD call center and WorkSource operate somewhat separately and WorkSource agents can sometimes reach technical people the call center can't.

0 coins

Went to a WorkSource location when I was stuck on a different issue and they were actually able to conference in an ESD technical person on the spot. Way more effective than calling the main line.

0 coins

Updating everyone who helped - finally got through to an ESD agent using a combination of things from this thread. The agent found two issues: a corrupted session token sitting on my account from my first failed attempt, and my SAW assurance level was at basic rather than medium. They cleared the session token and walked me through upgrading the assurance level. The application submitted successfully about an hour after the call. Benefit year officially started. Thank you all genuinely - this thread had better troubleshooting information than anything on the ESD website.

0 coins

Both issues hitting at once explains why the browser fixes weren't working - you were dealing with a backend problem AND an assurance level problem simultaneously, and fixing one wouldn't have fixed the other.

0 coins

Two-layer problems like this are exactly why you need to actually talk to an ESD agent rather than trying to solve it through browser troubleshooting alone. Glad getting through to someone worked out.

0 coins

really glad this got resolved - two weeks of delay on starting your claim because of a system bug is genuinely harmful and ESD should have better tools for people to self-identify these kinds of issues

0 coins

Washington Unemployment AI

Expert Assistant
Secure