Back to Washington State FMLA

Luca Esposito

Washington paid family leave login keeps throwing me out — can't file my weekly claim

Every time I try to get into my Paid Leave account to file my weekly claim, SecureAccess Washington kicks me out before I even get to the claim screen. I log into SAW, it looks like it's loading, and then I end up back at the SAW homepage like nothing happened. I've tried Chrome, Firefox, cleared my cache twice, and nothing works. I took medical leave two weeks ago for a surgery on my lower back and I finally got the Approved status last week. Now I actually need to file and I can't even get in. Is this a known issue? Am I missing something obvious with the SAW login? I don't want to miss the window for filing these weeks.

The SAW login loop you're describing — landing back at the homepage after it loads — usually means the Paid Leave service isn't properly linked to your SAW account. When you're in SAW, there should be a list of your services and "Paid Leave" should be one of them with a button to go to your benefit account. If it's not there, or if the button doesn't take you in, that's the connection that's broken. You'd need to phone the Customer Care Team at 833-717-2273 to get them to link it again.

0 coins

It does show Paid Leave in my services list in SAW, it's just the loading that fails. So the link is there, it just doesn't follow through.

0 coins

Cookies could be blocking it too. Third-party cookie settings in some browsers block SAW from finishing the handoff to the Paid Leave account. Trying a different browser with default settings sometimes clears it.

0 coins

Tried a fresh browser profile with no extensions and it did the same loop. Going to try a different device tonight.

0 coins

30 days after the week ends is the window for filing each weekly claim — I panicked about that when I was first figuring this out. Each week runs Sunday through Saturday, and you file after the week closes. Missing the whole window was what I was scared of, but the two weeks of approved leave sitting there waiting aren't going anywhere just because you can't log in today. Get the access fixed first.

0 coins

The 30-day detail is worth double-checking directly with Paid Leave — I've seen different numbers float around and I'd hate for someone to cut it close based on a forum post.

0 coins

Fair enough, I'd say ask Paid Leave to confirm the exact cutoff for your own weeks rather than relying on what I said. The point is you're not losing those weeks overnight.

0 coins

Good to know there's some buffer. Getting into the account is still priority one but at least I'm not in a 24-hour emergency.

0 coins

The third week of approved leave on my own claim hadn't paid out and I couldn't tell if the weekly claim had even gone through. Used Claimyr (claimyr.com) to get a live Paid Leave agent on the phone — I had Claimyr sit on hold while I went back to work, and when a specialist picked up I was already on the line. The agent pulled up my claim and told me the weekly claim for that week had been received and that payment was processing, with the funds expected to load within five business days from the approval date. Claimyr's video on reaching a live person at Washington Paid Leave: https://youtu.be/8Z3gABfzI50

0 coins

Five business days from approval is useful to know. Did you have the same SAW login problem or was your issue just the payment timing?

0 coins

No login issue on my end, just couldn't see any movement on the payment side. The agent confirmed the claim was filed correctly and the week was processing, which was all I needed.

0 coins

My second weekly claim took longer than five days. The first one landed on day four, the second stretched to day seven. The agent I eventually reached said the first approval sometimes moves faster because the account is fresh.

0 coins

The Technical Support page on Paid Leave's site has a list of browser settings that SAW requires — specific security settings that need to be enabled. I had to adjust my browser's TLS settings once to get past a similar block. Might be worth checking that before anything else.

0 coins

The TLS angle is worth trying, though for most people clearing cookies and switching browsers handles it. The Technical Support page does walk through the common fixes step by step.

0 coins

Found the Technical Support page. Going through the checklist now. The SAW system definitely has quirks that aren't obvious from the outside.

0 coins

My claim got Approved last month after two weeks In Review and I had the same stomach-drop feeling when I tried to file the weekly claim and couldn't see the right screen. Turned out I was clicking the wrong section entirely — the weekly claim button was under the Current Claim box, not under Take Action where I kept looking.

0 coins

Mine actually fails before I get to any section — the loading itself stops and dumps me back to SAW. But I'll double-check where the button lives once I can get in.

0 coins

Ah, that's a different problem then. Sounds like the SAW-to-Paid-Leave handoff is breaking somewhere in the middle for you.

0 coins

Happened to me twice on the same day once. Second time I waited twenty minutes and tried again and it worked. No idea why, but it did.

0 coins

Paper applicants have to file weekly claims by phoning the Customer Care Team instead of doing it online — that's the rule. If you genuinely can't get the online account working in time, calling in and filing by phone might be an option to ask about. Though online applicants are normally supposed to file online, so you'd want to confirm whether they'll accept a phone filing in a technical emergency.

0 coins

Phoning to file as a backup in a technical emergency is worth asking about, but I wouldn't assume it without confirming. The rep might just troubleshoot the login with you instead of accepting a phone claim for an online account.

0 coins

Exactly right — ask first, don't just assume they'll take it. The point is there's a path forward even if the account stays broken tonight.

0 coins

The claim year end date was something I'd completely lost track of — my leave started in late November last year and I'd assumed the year reset in January. It doesn't. The claim year is 52 weeks from the Sunday of the week your leave started or the week you applied, whichever is earlier. I had Claimyr hold the line for me while I was dealing with a complicated schedule and ended up speaking with a Paid Leave specialist who confirmed my claim year runs through mid-November and that I still had hours left. That was a relief because I thought I'd used everything up.

0 coins

The claim year starting from your first week rather than a calendar year threw me off too. The 52-week count from that specific Sunday is easy to miscalculate if you're not tracking it carefully.

0 coins

Does the typical workweek hours figure stay the same even if you change jobs partway through the claim year? Asking because my hours shifted after I came back from leave.

0 coins

The agent told me the typical workweek hours and weekly benefit amount stay fixed for the whole claim year, based on what was set when the claim was approved. A job change doesn't reset those numbers — you'd update your current employer in the account but the benefit amount holds.

0 coins

Updating the current employer is done through the Take Action section in the account. The benefit calculation itself doesn't change mid-claim-year, so your payment amount stays what the decision letter says.

0 coins

Browser extensions were killing my SAW login for two months before I figured it out. Had an ad blocker that was quietly blocking a script SAW needs to redirect you into the Paid Leave account. Disabled everything, got straight in. Now I keep a bare browser profile just for government logins.

0 coins

Already tried a fresh profile with no extensions and got the same loop. It's something deeper than extensions on my end, I think.

0 coins

If a bare browser profile doesn't fix it, the next step is probably a completely different device — phone or tablet rather than your usual computer. That rules out anything machine-specific.

0 coins

A phone's browser often works better for SAW than a desktop with a lot of customization. I do all my government account stuff from my phone now for exactly this reason.

0 coins

Medical leave for your own condition does have a waiting week — the first approved week you claim doesn't pay out. Back surgery recovery would fall under medical leave. It's one of the things that caught me off guard when my first week came up empty. The weeks after the waiting week pay normally.

0 coins

The waiting week detail is accurate for medical leave. Worth noting that if the leave were family leave to bond with a new baby, there'd be no waiting week — but for the poster's own surgery, that first week is unpaid.

0 coins

I did see something about the waiting week in the decision letter. So the second week is the first one that actually pays out for my situation. At least I know that going in.

0 coins

Paying any bills during the gap while the account was inaccessible and the weekly claim was unfiled was what stressed me most when I hit a login snag. Knowing payments come three to five business days after the weekly claim is approved helped me plan, but it still felt tight.

0 coins

The three-to-five business day window is after the claim is approved for payment, not after you file it. The processing of the claim itself can take up to 14 days under the law, and then the bank processing adds those additional days. So total time from filing to money in hand can stretch further than people expect.

0 coins

That's a fair correction — I conflated the two steps. The 14-day processing clock and then the 3-5 day bank processing are separate. Good to know that going in.

0 coins

The Paid Leave account has a Message Center where you can send a secure message if phoning isn't working out. That assumes you can actually get into the account, which is the whole problem here — but if you can get in long enough to reach that screen, sending a message about the login issue itself might at least start a paper trail.

0 coins

Catch-22 if the login is broken. Though if I can get in on a different device I'll do exactly that.

0 coins

Secure messages do get responses, but it's not fast. Phone got my issue sorted the same day; a secure message I sent before that took four days to get a reply.

0 coins

A request for review I filed after my medical leave was partially denied sat in Submitted status for longer than I expected. Had Claimyr hold the line so I could reach a Paid Leave specialist without spending my whole lunch break on hold, and ended up talking to someone who pulled up the review and told me it was In Review status, with the certification form for the disputed weeks listed as received. No missing documents on their end — the review was just moving through the queue. Knowing it was In Review and nothing was missing let me stop second-guessing whether I'd uploaded everything right.

0 coins

The review statuses mirror the application statuses in a way — Submitted, In Review, then Review Complete. Getting confirmation that the certification was showing as received is the kind of thing that's impossible to verify from the account alone.

0 coins

Exactly. The account shows the status but doesn't tell you whether a specific document is there. The agent seeing "received" next to the certification was what I actually needed to know.

0 coins

The decision on the review comes in a letter, same as the original decision. If you disagree with that too, the appeal has to go by mail or fax within 30 days of the notification date on the letter.

0 coins

Different device fixed a nearly identical login issue for me. Phone worked perfectly when my laptop kept looping back to the SAW homepage. Something about how mobile Safari handled the redirect from SAW to the Paid Leave account was just cleaner than whatever my laptop's browser was doing.

0 coins

Trying on my phone tonight. At this point a different OS and browser is worth a shot.

0 coins

Log in to SAW on the phone's browser first, make sure Paid Leave is in the services list, then click through. It went straight in for me on the first try after two days of laptop failures.

0 coins

The direct deposit option is set up in the account after you're approved — if the login issue persists past the point where your first payment would process, the payment would go to the prepaid ReliaCard by default if direct deposit isn't set up. The card gets mailed after you submit the application, so it may already be on its way.

0 coins

I did set up direct deposit when I first applied, before the login issue started. So that should be fine as long as the banking info is still in there.

0 coins

Banking info stays saved in the account. As long as you set it up during the application and haven't had any account changes, it should still be active.

0 coins

Keeping the banking information current is worth checking when the login is fixed. If anything got out of sync during a SAW account issue, confirming the payment method is set right before the first payment processes saves a headache.

0 coins

The Customer Care Team number is 833-717-2273 and hours are Monday through Friday, 8:30 to 4:30. Calling earlier in the morning tends to have shorter waits in my experience, though I've had mixed results even at 8:30.

0 coins

Earlier does help but it's not guaranteed. The hold times vary a lot by day and time, and there's no reliable pattern to predict which day will be fastest.

0 coins

Tried 8:30 on a Monday once and was still on hold for a long stretch. Mid-week mornings worked slightly better for me but nothing felt reliable.

0 coins

The SAW account and the Paid Leave account are technically two separate things — SAW is just the door. If SAW ever gets deleted or disconnected, you'd need to phone Paid Leave to link your Paid Leave account to a new SAW account. That's one of the specific things that takes a phone call. Might not be your situation, but worth ruling out.

0 coins

My SAW account is definitely still active, I can see other services in it. The Paid Leave link is there, it just doesn't complete the handoff. So it's something between SAW and the Paid Leave side.

0 coins

In that case the most direct fix is probably a phone call to Paid Leave specifically about the handoff failing. They can see from their side whether the account link is healthy or if something's broken in the connection.

0 coins

Leave in the postnatal period works differently for a birth parent than general medical leave — it counts as medical leave by default for those first six weeks. I got confused about which kind of leave I was filing for initially, but it doesn't change how the weekly claim works. You still file one for every approved week, same process regardless of which type of leave it is.

0 coins

The poster's situation is back surgery, not a birth, so the postnatal point doesn't directly apply here. Though it's worth knowing for anyone reading who is a birth parent figuring out the two-application setup.

0 coins

True, I went off on a tangent. For the poster — medical leave for a surgery, file a weekly claim for every approved week, waiting week applies to the first one.

0 coins

Proof of ID and the certification form being uploaded doesn't guarantee the account access works smoothly afterward. Those are on Paid Leave's document side, and the SAW login issue is on a different system entirely. Two separate headaches that can stack on each other at the worst time.

0 coins

The document side and the account access side being separate systems is a genuinely underappreciated point. Paid Leave can have all your documents received and your application Approved while your SAW login is completely broken and unable to reach the weekly claim screen.

0 coins

That's exactly where I am. Everything is Approved, documents are in, and the login is the one remaining wall. Good framing — it means the claim itself is healthy, just the access is broken.

0 coins

Employer letters go out from Paid Leave once an application is submitted and again when it's approved or denied — they don't include any medical info, just dates and the fact of the leave. Knowing that helped me feel less exposed about my employer seeing anything about the surgery itself.

0 coins

The employer letters not containing medical information is one of those things that isn't obvious until you read the fine print. Hours, wages, the weekly benefit amount — none of that is in what the employer receives either.

0 coins

Exactly. The employer sees the leave dates and application status, nothing about why or how much. That separation is built into how the program works.

0 coins

Filing the weekly claim for a week you didn't want any benefits for still matters — you're supposed to file one for every week of the approved leave period, even if you worked the whole week or didn't need anything. Skipping a week doesn't pause the clock; the claim year keeps running.

0 coins

Does that mean if you file a weekly claim and report enough hours worked that the payment would be zero, the waiting week still counts as your waiting week even with no payment?

0 coins

The waiting week is the first week you claim — it's not paid regardless of hours. After that, your hours worked and paid time off reported can reduce or zero out a week's payment, but the waiting week is specifically the first claimed week, not a function of the hours math.

0 coins

To add to that: if you used paid time off from your employer during the waiting week, you can use it without it affecting your benefits. The waiting week itself won't pay, but the PTO doesn't count against anything either.

0 coins

Logging out of SAW completely, closing the browser, reopening, and logging back in fresh — not just refreshing the page — fixed a redirect loop for my husband when he was setting up his bonding leave account. The session sometimes gets stuck mid-auth and needs a full reset to clear.

0 coins

Full logout and fresh session is next on the list to try. I'd been refreshing or just closing the tab, not fully logging out of SAW first.

0 coins

Full SAW logout is the key part. Closing the tab leaves the session active in some browsers, so the loop just resumes where it left off.

0 coins

Incognito or private browsing mode also forces a fresh session without saved cookies or an active SAW session. Might be faster than tracking down where to fully log out.

0 coins

Washington State FMLA AI

Expert Assistant
Secure