Back to Nevada Unemployment

Lena Kowalski

Unable to file weekly claim unemployment - what's happening with my Nevada DETR account?

Okay so I'm losing my mind a little bit here. I've been on unemployment for about six weeks now and everything was going smoothly until this past Sunday when I tried to submit my weekly certification and the whole thing just... stopped working. I log into the CSS portal at nui.nv.gov and my weekly claim option is completely grayed out. No error message, no explanation, nothing. It just won't let me click through. My situation: I was laid off from a logistics coordinator position at the end of February. Regular UI claim, no issues with my initial filing, got approved after about 10 days. I've been doing my four job search activities every week, logging everything in EmployNV, no missed certifications up until now. I tried logging out and back in, different browser, even my phone. Same result every time - the weekly claim filing option is just inaccessible. My claim status still shows as active, nothing flagged, no adjudication notice, no correspondence in my message center. It's like the system just decided to stop letting me file without telling me why. Has anyone else run into this where their Nevada DETR account looks totally fine but they're unable to file weekly claim unemployment benefits? I'm worried that if I can't get this resolved I'm going to miss my certification window and lose benefits for that week or worse. Any help would be appreciated.

Week 14 of my own claim and I hit almost this exact same wall back around week 8. The grayed-out button thing is usually one of two things: either your claim has been quietly flagged for a review (which doesn't always generate an immediate notice), or there's a system-side issue on CSS that's affecting your specific account. The maddening part is you won't always get a notification either way. What I'd check first: go into your claim summary and look at whether your benefit year end date is still far out. Sometimes when claims get close to exhaustion or hit certain thresholds the system locks you out pending a manual review even if you have weeks remaining. Also check if there's anything pending under the 'Issues' tab - sometimes flags show up there before any formal notice goes out.

0 coins

Went back and checked both of those things. Benefit year end is still months away and the Issues tab shows absolutely nothing pending. That's what's making this so confusing - there's no trail to follow.

0 coins

My third week trying to certify I had the same empty Issues tab and it turned out there WAS a flag, it just hadn't populated yet. Took another two days before it showed up. So it might be worth checking again in 24-48 hours.

0 coins

48 hours before the certification deadline I'd still be panicking honestly. The system not showing the flag doesn't mean there isn't one brewing behind the scenes.

0 coins

Six days into dealing with something similar last month and I finally got it sorted but only because I was able to actually reach someone at Nevada DETR by phone. That's easier said than done obviously - I tried the main line for days and kept getting the 'high call volume' disconnect. What ended up working was using Claimyr (claimyr.com). It basically holds your place in the queue and calls you back when an agent picks up instead of you just sitting on hold forever. There's a video walkthrough at https://youtu.be/Mc9FNfOF_yY if you want to see how it works before trying it. The agent I finally reached was able to see exactly what was blocking my weekly filing and pushed through a fix on their end within like 10 minutes. Some of these account locks genuinely cannot be resolved without a live agent touching the account.

0 coins

Trying this today because I've already spent two mornings hitting redial with nothing. If a live agent is the only way to actually unlock whatever's happening on the backend I need to find a way to get to one. Thanks for the tip.

0 coins

Seconding this approach. There's a certain category of CSS account issues that the online help documentation just does not cover and phone is the only path.

0 coins

I was skeptical of anything that promised to get through to Nevada DETR faster but honestly at a certain point you just need results.

0 coins

Somewhere around day four of a similar lockout I discovered that CSS has a known bug where if you log in from a mobile device at any point during the certification period it can corrupt the session and prevent desktop filing for the rest of that week. I know that sounds absurd but it's a real thing. Try this: clear every cookie and cached file from your browser, then log in ONLY from a desktop or laptop using Chrome or Firefox, and don't touch your phone login until after you've successfully submitted. Some people also had luck using an incognito/private window so there's zero cached data interfering.

0 coins

Clearing everything now and switching to an incognito window on my desktop. I had definitely checked on my phone earlier this week so this might actually be it.

0 coins

This is real - the mobile session conflict thing. I read about it on another forum and my nephew had the exact same issue resolved just by clearing cache and not mixing devices.

0 coins

Worth trying but I'd keep the phone call option as a parallel track just in case. These workarounds don't always stick.

0 coins

Just finished week 11 of my claim and I want to flag something that might be relevant. The 72-hour window they give you to file your weekly certification isn't as forgiving as it sounds - if any kind of system hold gets placed on your account even one hour before your window closes, you lose that certification week entirely unless an agent manually reopens it. I found this out the hard way. The rule is buried in the claimant handbook but basically: account holds and certification deadlines don't pause for each other. So if you're in a lockout situation right now, the clock is still running on your weekly window even while you're trying to fix the problem.

0 coins

This is genuinely alarming. So I'm racing against my certification deadline at the same time I'm trying to diagnose why I can't file? That feels like the system is designed to make you fail.

0 coins

Yeah the deadline doesn't pause for technical issues unfortunately. I lost a week to this exact scenario. Best thing you can do is document everything - screenshot your CSS screen showing the grayed out button with the timestamp visible, so if you need to appeal a missed week you have proof.

0 coins

Screenshot everything is excellent advice. I'd add: also save any emails or messages you sent to DETR trying to reach them during the lockout period. Paper trail matters a lot in appeals.

0 coins

My claim hit a weird snag around the same time - week seven - and what an agent told me was that a system update rolled out that caused some accounts to require a re-verification of job search activity logs before the weekly filing option would reactivate. Apparently it wasn't pushed out consistently so only certain claimants got hit with it. If that's what happened to you, the fix is to go into EmployNV, make sure all four of your weekly job search contacts are logged with complete employer information and contact method, then wait up to 24 hours for the systems to sync. The CSS portal and EmployNV don't update in real time - there's a lag that can cause the filing option to stay locked even after you've done everything right.

0 coins

Going into EmployNV right now to double-check all my entries. I thought I had everything complete but maybe something is missing that's triggering the hold.

0 coins

The sync lag between EmployNV and CSS is so annoying. I had complete job search logs and my portal still showed them as pending for almost two full days.

0 coins

Does anyone know if the sync lag affects the certification deadline? Like does it count as filed if you submit within your window even if EmployNV hasn't synced yet?

0 coins

This whole thread is exactly my current nightmare except I'm at week 3 and already dealing with a lockout. Can I ask - does anyone know what happens if you genuinely cannot file within your certification window due to a system error? Like is there any official process to get a missed week reopened or do you just lose it forever?

0 coins

There IS a process but it's not simple. You have to contact Nevada DETR and explain the technical issue, provide documentation (screenshots, timestamps), and request that the week be reopened for late filing. It's not guaranteed - an agent has to manually authorize it and some will and some won't. I've seen people get it approved and I've seen people get denied.

0 coins

Filing an appeal is also an option if they deny the late filing request. The appeal process for a missed certification week is different from an adjudication appeal - it goes through the same general appeals system but the grounds are specifically the technical failure.

0 coins

I lost a week last year to this and never got it back. I didn't know about the documentation thing until it was too late. Screenshot EVERYTHING the moment you notice a problem.

0 coins

Three weeks after my own certification lockout I'm here to say it does eventually get resolved but the process is painfully slow without direct agent contact. I want to push back a little on the idea of just waiting it out or trying browser fixes - in my case the account had been flagged by an automated review trigger and NO amount of cache clearing or waiting for syncs was going to fix it. Only an agent could remove the flag. The system doesn't tell you this. You just sit there refreshing and trying different browsers while the certification window closes around you.

0 coins

This is exactly what I'm afraid of. How long did it take you from the time you got through to an agent to when the fix actually showed up in your portal?

0 coins

Honestly about 20 minutes total once I had the agent on the line. The agent saw the flag immediately, removed it, told me to wait 15 minutes and try again, and it worked. The problem was getting to an agent took me three full days of calling.

0 coins

Three days of calling is a full-time job in itself. The hold times at Nevada DETR are genuinely brutal.

0 coins

Fourteen attempts to reach DETR by phone over two days and I was absolutely losing it. Someone in another thread mentioned Claimyr and I was skeptical but desperate. Used it, got a callback within a couple hours, agent picked up, had my weekly filing unlocked same day. The specific thing blocking mine turned out to be an identity verification flag that had been sitting dormant since my initial claim and just suddenly activated when I hit a certain week threshold. No notice, no warning. The agent said these automated flags are more common than people think and they almost always require a live agent to clear. Worth knowing the site is claimyr.com in case anyone else is burning through their certification window right now.

0 coins

Reached out through that site today actually. Waiting on the callback. Fingers crossed the agent can see whatever flag is sitting on my account.

0 coins

Identity verification flag sitting dormant is terrifying honestly. So there could be a flag on anyone's account that just hasn't activated yet?

0 coins

The dormant flag thing is a real quirk of how the CSS system handles claims that were initially approved without full verification. If your initial adjudication went fast (like less than 2 weeks) there's a decent chance the system flagged it for follow-up verification later and you just haven't hit that trigger point yet.

0 coins

Just got through week 9 of my claim with no issues so far but reading this thread is making me anxious. Quick question for anyone who knows - if your weekly claim filing option is grayed out but you don't see a flag in the Issues tab, is there any other place in CSS where a hold or flag might be visible? I want to know what to look for before it happens to me.

0 coins

Check the 'Correspondence' section in CSS for any letters that might have been generated but not yet flagged as 'requiring action.' Sometimes a letter goes out that doesn't trigger the Issues tab but still puts a soft hold on the account. Also look at your payment history - if you see a week that shows 'pending' rather than 'paid' or 'denied,' that sometimes precedes a lockout.

0 coins

The claim summary page sometimes shows a 'pending review' status in small text under your claim number that most people overlook. It doesn't flag as an issue but it does mean something is in review.

0 coins

Checking all of this right now, thank you. The 'pending review' text under the claim number is something I never would have thought to look for.

0 coins

Week 2 of my claim and already hit a minor version of this - my filing option was accessible but kept throwing an error at the final submission step. Different from the full lockout but similarly maddening. What fixed it for me was logging out, waiting a full hour, then logging back in and completing the certification in one continuous session without navigating away from the page. The CSS system seems to time out the certification session faster than the visible timeout warning suggests.

0 coins

Keeping the session open without navigating away is good advice I hadn't tried. Though at this point I can't even get to the submission step - the button is fully inert.

0 coins

The session timeout thing is a real annoyance. I always do my weekly certification in one shot now specifically because of this.

0 coins

My first week filing I navigated away to check something and came back to find my partial claim had vanished. Had to start over. Definitely finish it in one go once you start.

0 coins

Something nobody has mentioned yet: the certification window for Nevada UI opens Sunday and closes Saturday but the EXACT time it opens Sunday can vary. I found out the hard way that trying to file right at midnight Sunday sometimes catches the system mid-reset and you get ghost errors or inaccessible buttons that resolve on their own by mid-morning. If you tried to log in very early Sunday morning, that might explain a temporary lockout that doesn't show any flag.

0 coins

I tried Sunday evening so it wasn't a midnight reset issue. But good to know for the future - I had no idea there was a system reset window in the early morning.

0 coins

The Sunday midnight reset thing is real. I burned two hours one Sunday trying to file at like 1am before realizing the system was essentially rebooting. Came back at 9am and filed in two minutes.

0 coins

Why would they schedule system maintenance during the certification window? That seems like a design failure.

0 coins

Wrapping up week 17 of my claim and want to add something for people dealing with lockouts: always check whether your Nevada DETR message center has an unread message marked as 'action required' that you might have missed. The CSS notification system is inconsistent - sometimes messages sit unread without any visual indicator on the main dashboard and the system won't let you advance to weekly filing until you open and acknowledge them. I had one sitting there for four days once that I completely missed.

0 coins

Went back through every message in my center including old ones. Nothing marked as action required anywhere. I really am starting to think this is a backend flag that's invisible to me.

0 coins

If there's nothing in correspondence and nothing in issues and the button is just grayed out with no explanation, you're almost certainly looking at an automated hold that only an agent can see and remove.

0 coins

This is basically confirmed at this point. OP needs an agent. The system just doesn't surface these flags to the claimant.

0 coins

Just want to validate the OP here because I went through almost exactly this and the emotional toll of not being able to file when you need that money is real. I spent an entire week cycling through every suggestion I could find online, clearing cache, different browsers, different devices, checking every tab in CSS, and nothing worked. It turned out to be a completely invisible automated flag. The fix took an agent about eight minutes once I got through. Eight minutes versus five days of stress.

0 coins

Hearing this actually makes me feel a little better about not having solved it yet. If even doing everything right doesn't fix it and only an agent can, then at least I'm not missing something obvious.

0 coins

You're definitely not missing something obvious. These invisible flags are a known issue and the system really should notify people when one gets placed. It doesn't, which is a failure of the platform.

0 coins

The lack of notification for automated holds is a legitimate complaint. You'd think an email at minimum would be triggered when something prevents you from filing.

0 coins

For context on where things stand with the CSS phone situation in general: the main Nevada DETR UI line does have extended hours but the volume is still high enough that getting through before your certification deadline can be a genuine race. If you're in a lockout right now and your window closes in less than 48 hours I would not rely on the standard call-in method alone. Document everything you can, pursue parallel tracks (phone, online inquiry submission, in-person at a local Nevada JobConnect office if one is accessible), and keep trying.

0 coins

In-person at a JobConnect office is something I hadn't thought of. Is that actually an option for CSS/portal account issues or only for job search stuff?

0 coins

JobConnect staff can't always fix CSS account issues directly but they can escalate to DETR and sometimes get faster internal triage than a standard phone call. Worth a shot if you're out of options before the deadline.

0 coins

I didn't know JobConnect could escalate to DETR for account issues. That's actually useful to know.

0 coins

My situation last month: hit week 5, button grayed out, spent three days trying everything. Finally used Claimyr to get through to an agent - claimyr.com - and when the agent pulled up my account she said there was a re-determination review flag that had been placed automatically because my reported earnings from one partial week were processed in a way that triggered a secondary check. The flag was completely invisible to me in the portal. She removed it in real time while I was on the phone. I want to be clear that I had checked the Issues tab, the Correspondence section, the claim summary, everything - there was no visible indication of this flag anywhere I could access as a claimant.

0 coins

So the agent confirmed there's a whole class of flags that just don't surface to the claimant at all. That's actually useful to know going into my own call.

0 coins

Re-determination review flags from earnings processing sounds like exactly what might be happening to me too. I had one partial week in my claim.

0 coins

Partial week earnings are honestly such a common trigger for these invisible flags. I wish DETR would just be upfront about it.

0 coins

Around week 4 of my own claim I ran into a variation of this where the filing button was accessible but disappeared after I answered the first question. Completely different from the grayed-out version but same result - couldn't file. The issue turned out to be that my job search activity log in EmployNV had one entry with an incomplete employer address field, which CSS was reading as a failed verification even though the entry showed as complete on my end. If you have any job search entries that you filled in quickly or copied from a previous week, go back and make sure every field has substantive content, not just placeholders.

0 coins

Double-checked all my EmployNV entries and every field looks complete to me but I can see how a partially filled field might look fine from the claimant side while CSS reads it as incomplete.

0 coins

The CSS validation rules for EmployNV entries are stricter than what EmployNV itself enforces when you save the entry. So something can pass the EmployNV save step but fail the CSS validation.

0 coins

This explains why my claim got held up despite having all four contacts logged. One of them had a phone number field I'd left blank because I applied online. That was apparently enough to trigger a validation failure.

0 coins

Quick update thread for anyone following: submitted an online inquiry through the CSS message center this morning explaining the lockout and my certification deadline. Got an automated response acknowledging the inquiry. No actual help yet but at least there's a timestamp on record showing I tried to resolve it before my window closed. If this ends up requiring an appeal later I want every possible documentation of when the problem started and what I did to fix it.

0 coins

This is exactly what I've been doing too - creating a paper trail just in case. Screenshot of the grayed-out button with timestamp, record of every call attempt, the online inquiry submission. If I miss this week's certification and need to appeal, I want to show I did everything possible.

0 coins

The online inquiry timestamp is actually a solid move for appeal documentation. It's official correspondence with DETR that shows you were actively trying to resolve the issue, not just ignoring the certification.

0 coins

Appeals for missed certifications due to system errors do go through. I've seen a few people on this forum report successful appeals specifically because they had timestamped documentation of the lockout and their attempts to fix it.

0 coins

Coming in late to this thread to share my resolution because I think it'll be useful for people still in the middle of this. I was unable to file weekly claim unemployment benefits for almost a full week due to an invisible automated flag - no notice, no visible issue in CSS, nothing. I ended up using Claimyr (claimyr.com) after burning through every other option. When the agent finally picked up she was able to see a dormant identity cross-check flag that had activated because my SSN verification had been queued for secondary review during my initial claim processing and never fully cleared. The agent submitted an internal resolution ticket and my filing button was live again within two hours. Total phone time with agent: maybe 12 minutes. Time spent trying to fix it on my own: six days.

0 coins

This is basically my situation resolved by proxy. The SSN secondary review thing is new information - I was laid off quickly and my initial claim processed fast (under 10 days approved), so it's very plausible something in my verification got queued and never cleared.

0 coins

The fast initial approval being a possible trigger for a later verification flag is counterintuitive but makes a certain bureaucratic sense. The system approves quickly then kicks off a background verification that sits in a queue until it hits a threshold.

0 coins

Whether it's SSN verification, identity cross-check, earnings review, or EmployNV sync - the common thread here is that they're all invisible to the claimant and all require an agent to resolve. The CSS system really needs a 'your account has a pending internal review' notification at minimum.

0 coins

Nevada Unemployment AI

Expert Assistant
Secure