Back to Arizona Unemployment

Luca Marino

Arizona DES unemployment you do not have an eligible current claim file new claim message - what does this mean?

Logged into CACTUS this morning to certify for my weekly benefits and got hit with a message I've never seen before: 'you do not have an eligible current claim file new claim.' No warning, no explanation, nothing. My last payment went through fine two weeks ago and I haven't had any issues with my job search activities or anything like that. I've been on UI for about four months after getting laid off from a logistics company in February. Did something expire? Did I mess something up on my weekly certification? I'm completely lost and kind of freaking out because rent is due in ten days. Has anyone seen this message before and what does it actually mean?

Benefit year expiration is almost certainly what happened here. Arizona DES sets up your claim with a 52-week benefit year, and once that window closes, the system cuts you off automatically even if you still have a remaining balance. The message you're seeing is the portal's way of telling you the original claim period ended. If you filed back around February, that tracks with a year-end cutoff landing right about now - wait, actually four months in doesn't add up to a full year. Could be something else. Did you recently report any wages or change your availability status on a weekly cert?

0 coins

No wages to report at all, been fully unemployed the whole time. Availability hasn't changed either. I mark myself as able and available every single week without fail.

0 coins

Benefit year thing is real but four months is way too short for that. More likely a base period wage issue or they flagged something on a recent cert.

0 coins

Yeah I was second-guessing myself on the timeline. Good catch. OP should look at whether there's a pending issue or disqualification notice in their message center on CACTUS they might have missed.

0 coins

Claimyr got me through to an actual Arizona DES agent in under an hour when I had an almost identical portal error last spring. The normal phone lines are brutal - I spent three days redialing before I found it. You enter your info at claimyr.com and they basically navigate the hold queue for you and call you back when an agent is on the line. There's a video at https://youtu.be/vwA1GGuV83Y showing exactly how it works. For a situation like yours where the portal is blocking you from certifying, talking to a live agent is really the only way to get a straight answer fast.

0 coins

Rent situation is making me seriously consider this. The idea of actually getting through to someone instead of burning hours on hold sounds worth it.

0 coins

Second this. Phone queue at Arizona DES is genuinely awful, especially mid-week. Any shortcut to a real human is worth knowing about.

0 coins

does this work for people who've never filed before too or only existing claimants

0 coins

First thing I'd do in your spot - pull up every notice in your CACTUS message center going back at least 30 days. Arizona DES sends disqualification notices, eligibility alerts, and issue flags through the message center and a lot of people never check it because they're just logging in to certify. The system can flag your claim for all kinds of reasons: they detected a discrepancy in your reported hours, an employer contested something, or even a database glitch. The message you're describing doesn't always mean your claim is gone forever - it can mean there's a hold that needs to be resolved before you can keep certifying.

0 coins

Just checked every message in there going back to January. Nothing flagged, no disqualification notices, no pending issues listed anywhere. The message center looks completely clean.

0 coins

That's actually more confusing in a way. When there's nothing in the message center but the portal blocks you anyway, it usually means the issue is on the backend and you genuinely need a phone call to sort it out.

0 coins

Agreed. Clean message center plus that error usually points to a system-side thing. An agent can pull up what's actually happening on the account.

0 coins

Saw this exact message twice on my own claim. First time was when my benefit year actually did expire - I'd been on UI since the previous summer so the 52 weeks ran out. Second time was weirder: I had certified but the system apparently didn't process it correctly and threw that error on my next login. Both times the fix was filing a new claim through the portal. For your situation, since you're only four months in, I'd lean toward the second scenario - possible processing glitch. Try going through the 'File a New Claim' link it's pointing you to and see if it lets you pick up as a continuation rather than starting brand new.

0 coins

Tried clicking the file new claim button and it walked me through what looked like a full new application. Stopped partway because I didn't want to accidentally reset my existing claim or mess something up.

0 coins

Stopping was probably smart honestly. Filing a full new claim when you have an existing one can create duplicate claim issues that take weeks to untangle.

0 coins

Fair point, I didn't think about that. If your original claim is still technically active on the backend, an agent should be able to fix it without you having to refile completely.

0 coins

my cousin had this happen and it was because her employer went back and changed her separation reason after the fact. they originally put layoff but changed it to voluntary quit months later and DES flagged her claim and sent her into adjudication without ever notifying her properly. she only found out when she got that exact error message. worth considering if your former employer might have any reason to dispute the separation.

0 coins

Layoff was pretty clear-cut, they let an entire department go. But I hadn't even thought about the possibility of an employer going back and changing something after the fact. That's genuinely unsettling.

0 coins

Employer-initiated separation disputes can happen even with mass layoffs. Some companies try to reclassify separations after the fact to avoid UI charges on their account. It's not common but it happens.

0 coins

Yeah that's exactly what happened to her. The company was trying to dodge the rate increase on their account. She got it resolved eventually but it took about six weeks and an appeal.

0 coins

Six weeks with no income is brutal. Hope OP's situation resolves faster than that.

0 coins

BEEN THROUGH THIS NIGHTMARE. The portal error message is basically useless because it doesn't tell you WHY. Could be a dozen different things and the system just throws the same generic message for all of them. I spent two weeks trying to figure it out online before I finally got through to an agent who told me in about 90 seconds what the actual problem was. Arizona DES's self-service options are almost worthless for anything beyond basic certifications. You need a human on the phone.

0 coins

Two weeks before getting through - that's what I'm terrified of. Did you do anything specific to finally get someone on the line?

0 coins

Called right at 8am on a Tuesday, which apparently is slightly better than other times. Still took forever but at least I eventually got through. Good luck honestly.

0 coins

Tuesday and Wednesday mornings are supposedly the best windows but even then it's not guaranteed. The phone system is genuinely one of the worst I've ever dealt with.

0 coins

Something worth checking: when you log into CACTUS, look at the claim summary section and see if there's a benefit year end date listed. That date is different from when your money runs out. If that date has passed or is coming up very soon, the system will start throwing eligibility errors even if you technically have weeks of benefits remaining. Arizona DES requires you to file a new claim once the benefit year closes out, even if you're still in the middle of collecting. It's confusing because the balance and the year end are separate things.

0 coins

Benefit year end date on mine shows next January. So that's definitely not it.

0 coins

Okay so that rules out the year-end thing entirely. At that point I'd really say a phone call is unavoidable - this is something only an agent looking directly at your account can answer.

0 coins

January year end with four months of collecting, that lines up with a February filing. At least we know it's not an expiration issue.

0 coins

My neighbor used Claimyr for a situation almost exactly like yours - portal blocking her with no explanation, message center clean, couldn't get through on the phones. Agent she reached through claimyr.com looked at her account and found a flag that wasn't showing up anywhere on her end at all. Something about a wage crossmatch in the system that hadn't generated a visible notice yet. Got cleared up same day once she talked to someone. The video demo at https://youtu.be/vwA1GGuV83Y shows how the callback thing works if you want to see it before trying.

0 coins

Wage crossmatch is interesting - I did do some freelance work about two years ago and wonder if something from back then could resurface. Going to look into Claimyr tonight.

0 coins

The agent can see everything on the backend that isn't visible to you at all through the portal. That's really the value of actually talking to someone.

0 coins

wage crossmatch happened to my brother too. DES matched something from an old 1099 and it triggered an automatic review flag

0 coins

Filing a brand new claim when you already have an active benefit year is actually sometimes the right move but you have to be careful about timing. If your current benefit year is still open (which yours is, apparently), filing a new claim before it closes can create what Arizona DES calls a transitional claim situation and it gets complicated. I'd strongly suggest NOT filing the new claim the portal is suggesting until you've spoken to an agent and confirmed whether your current claim is truly closed or just erroring.

0 coins

This is exactly why I stopped partway through that new claim application. Instinct said don't do this without knowing more.

0 coins

Good instinct. Duplicate or overlapping claims can create overpayment situations that haunt you for years. Much better to verify first.

0 coins

Overpayment from an accidental overlap is genuinely one of the worst outcomes here. The portal pushing you toward 'file new claim' doesn't mean that's necessarily the right solution for your specific situation.

0 coins

ok so not to alarm you but have you verified that your identity verification is still current on your account? Arizona DES periodically requires re-verification through ID.me and if that lapses they can freeze claim activity without sending a super obvious notice about it. the error message might look like a claim eligibility issue but be an identity thing underneath

0 coins

ID.me verification - I did that back when I first filed but haven't been prompted to do it again. Where would I even check if that's expired?

0 coins

Log into your account and look for any ID verification section or pending tasks. Sometimes there's a banner or notification that's easy to scroll past. Also try logging directly into ID.me separately to check status there.

0 coins

This is actually a good call. Identity verification issues sometimes show up as generic eligibility errors rather than specific ID error messages.

0 coins

Adjudication is the specific process to understand here. When Arizona DES puts a claim into adjudication it means they're reviewing something before allowing continued payments. The tricky part is that adjudication can be triggered silently - a flag goes up on the backend, an agent reviews it, and in the meantime your ability to certify gets frozen. What you're calling a portal error might actually be your claim sitting in adjudication pending a decision. This is different from a true eligibility issue. During adjudication you're supposed to keep certifying if possible, or at minimum document that you've been meeting job search requirements, so you can receive backdated payments once it's resolved.

0 coins

Can you even certify if the portal is blocking you with that message? It won't let me get to the certification screen at all.

0 coins

That's the frustrating part - if the portal is completely blocking access, you may not be able to certify until the hold is lifted. Definitely document your job search activities and dates even if you can't submit them, and make a note of when you first saw the error.

0 coins

Documentation is so important here. When things get sorted out you'll want to be able to show you were actively searching the whole time, not just when the portal was working.

0 coins

adjudication is the word i was looking for when my claim got frozen. i kept calling it an audit which confused the agent i eventually talked to

0 coins

Just want to flag something nobody else has mentioned: sometimes this error appears because a weekly certification deadline was missed and the system essentially voids the certification period rather than just marking it late. Arizona DES has specific filing windows for each week and if you miss the window for a particular week, that week just closes out. This can sometimes cascade and affect subsequent certifications. Did you miss any weekly certification deadlines recently, even by a day or two?

0 coins

Two weeks ago I certified on a Sunday night which was cutting it close to the deadline. I'm not 100% sure if that one went through or not - I thought I saw a confirmation but I didn't save a screenshot.

0 coins

That could genuinely be it. A missed certification can sometimes flag the whole claim for review. Would be worth asking an agent to check if that specific week shows as certified or uncertified on the backend.

0 coins

Always screenshot your certification confirmations. Learned that the hard way myself.

0 coins

ugh this thread is giving me anxiety about my own claim. been certifying fine every week but now I'm paranoid something is going to randomly break. does DES send any warning before this kind of thing happens or does it always just appear out of nowhere

0 coins

Honestly? Often out of nowhere. The message center is supposed to give advance notice but it doesn't always work that way.

0 coins

great. so we're all just logging in and hoping for the best every two weeks

0 coins

Pretty much. Best you can do is check your message center regularly and document everything.

0 coins

Claimyr is worth trying here - went through a similar situation where my CACTUS account showed an eligibility block with no explanation and I finally got a callback to an agent through claimyr.com who resolved it in one phone call. The hold times on Arizona DES's direct lines had been running over two hours every time I tried. The demo video at https://youtu.be/vwA1GGuV83Y walks through exactly how it works. For a situation where you need a quick answer before a rent deadline, waiting days on hold isn't really an option.

0 coins

Rent deadline is in ten days so quick is what I need. Trying this tonight.

0 coins

Agent should be able to see exactly what triggered the block and either fix it on their end or tell you exactly what you need to do. Much better than guessing from the portal.

0 coins

two hours on hold is actually relatively short from what I've heard for DES lately lol

0 coins

Been lurking this thread and wanted to share what finally resolved mine. After weeks of that same error I called early morning and got through to an agent who found that my claim had been automatically suspended because a former employer had filed a wage record showing I'd earned a small amount during a week I had certified as having zero wages. The amount was tiny - turned out to be a final expense reimbursement my old employer had coded incorrectly as wages. Had to submit documentation showing it was a reimbursement and they lifted the suspension within two days.

0 coins

Expense reimbursement miscoded as wages - that's something I'd never have thought to check. I did get a small reimbursement for some tools right before my layoff.

0 coins

Worth mentioning specifically to the agent when you call. It's a common issue and they know exactly how to flag it for correction once they see it.

0 coins

This is probably the most useful specific scenario in this whole thread honestly. Reimbursements coded as wages happens more than people realize.

0 coins

The fact that something so small and routine can trigger a full claim suspension is genuinely wild. The system has zero tolerance for wage record discrepancies even when they're clearly clerical.

0 coins

One practical thing: when you do get through to an agent, have your social security number, claim ID, and the exact date you first saw the error ready before the call starts. Also write down every weekly certification date for the past two months. Agents can resolve things faster when you can answer their verification questions without digging around. The call will be short if you're prepared versus very long if you're not.

0 coins

Good list. Adding the certification dates to what I'm pulling together tonight.

0 coins

Also note the exact wording of the error message if you can. 'You do not have an eligible current claim' versus other variations can mean different things to an agent.

0 coins

Agents genuinely appreciate prepared callers. Had one tell me I was the most organized person she'd talked to all week which was both flattering and depressing.

0 coins

whatever you do don't file that new claim application until you know for sure your current benefit year is closed. I made the mistake of filing a new claim when I had a portal error and it created an overlap issue that took FOUR MONTHS to resolve. Arizona DES had to do a full manual review of both claims to figure out which weeks belonged to which claim period. It was an absolute nightmare and I went without any payments the entire time it was being sorted.

0 coins

Four months - that's terrifying. Really glad I stopped that new claim application partway through.

0 coins

If you didn't complete and submit it you're probably fine. The overlap issue only happens if the new claim was actually submitted and processed.

0 coins

This is why I always tell people: when the portal tells you to file a new claim, treat it as a suggestion to investigate, not a directive to actually do it immediately.

0 coins

Something that might be useful context here: Arizona DES sometimes runs scheduled maintenance that temporarily breaks claim access and throws weird error messages. It usually happens on weekends or overnight. If you first saw this on a weekend or late evening, try logging back in during normal business hours on a weekday before assuming it's a real issue. I know you're probably past that point at this stage but worth knowing for the future.

0 coins

First noticed it on a Monday morning so maintenance seems unlikely. But good to know that can be a thing.

0 coins

Maintenance window errors are real but they usually clear within hours. A persistent error showing up Monday morning is definitely not maintenance.

0 coins

Yeah Monday morning does rule that out. Just wanted to put it out there in case someone else finds this thread with the same message.

0 coins

Update us when you find out what the actual cause was. This thread has about four different plausible explanations and it would genuinely help other people searching for this error to know which one actually applied. Expense reimbursement, adjudication flag, missed certification, employer dispute - all real possibilities and knowing the actual answer helps the next person narrow it down faster.

0 coins

Will absolutely update. Going to call through Claimyr tonight and hopefully have an answer by tomorrow. Really appreciate everyone's input on this - went from completely panicked to having an actual plan.

0 coins

Good luck. Come back and let us know what the agent found on the backend.

0 coins

Rooting for the reimbursement explanation since that one has a clean fix.

0 coins

Updates on these threads genuinely help people. Most threads just go silent after the OP gets their answer.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure