Back to Arizona Unemployment

Liam Sullivan

Des unemployment claim pending weeks - verification issue anyone else?

Week four sitting here staring at the same 'pending' status on my CACTUS portal and I genuinely have no idea what's happening. I work in construction, laid off mid-February when the project wrapped up, filed my claim within a couple days. Everything seemed fine at first — submitted my documents, answered all the identity questions, got a confirmation number. Then nothing. Just... pending. The frustrating part is there's no explanation anywhere on the portal. No flag saying 'we need X from you' or 'we're waiting on Y.' Just pending. I've been filing my weekly claims every Sunday like you're supposed to, logging my job search contacts, doing everything right. But I'm watching my savings drain with zero communication from Arizona DES about what the hold-up actually is. I think it might be a verification issue because a friend of mine had something similar happen and they said Arizona DES needed additional ID documentation but never actually sent a notification about it. So I'm kind of guessing at this point. Has anyone else been stuck with their des unemployment claim pending weeks with a verification issue like this? Did you eventually get through to someone who could actually explain what was happening, or did it just eventually resolve itself?

Just hit week three myself on my pending status so I feel this post in my bones. Mine started after I uploaded my separation paperwork — employer submitted something that didn't match what I reported and now it's apparently in some kind of review. The portal really gives you nothing to work with does it.

0 coins

Week three and counting for you too — that employer mismatch situation sounds exactly like the kind of thing that would trigger a hold with no explanation. Did you at least get any paperwork from Arizona DES saying what the discrepancy was?

0 coins

Employer-filed information conflicts are actually super common and yeah, Arizona DES doesn't always send a notification. It just sits. Sometimes you won't know until you actually get a human on the phone.

0 coins

Five weeks was my personal nightmare earlier this year. What finally broke mine loose was figuring out that my identity verification through ID.me hadn't actually completed even though I thought it had — the portal showed verified but there was a secondary step I'd missed on the Arizona DES side specifically. If you haven't triple-checked your ID.me status AND your CACTUS account separately, do that before anything else.

0 coins

ID.me showing verified but still having a secondary step on the DES side — I didn't even know that was possible. Checking this right now actually.

0 coins

This happened to me too. The ID.me portal says complete but Arizona DES has its own verification flag that doesn't always sync up automatically. Worth logging into CACTUS and looking under account settings not just claim status.

0 coins

The two systems not talking to each other properly seems like such a basic thing to fix and yet here we are in 2025 still dealing with it.

0 coins

Finishing up week six of my own pending saga when I finally got some answers — but only because I actually reached a live Arizona DES agent. If you've been trying to call and getting nowhere, I'd seriously look into Claimyr. It's at claimyr.com and there's a demo video at https://youtu.be/vwA1GGuV83Y that shows how it works. Basically it handles the hold queue for you and calls you back when an agent picks up instead of you sitting on hold for hours. That's how I finally got someone to tell me my verification had a flag on it that wasn't visible from the portal at all.

0 coins

Six weeks before you got answers — honestly that's terrifying but also reassuring that there IS an answer eventually. The Claimyr thing is interesting, I've been burning through my phone battery on hold every other day.

0 coins

the hold times are genuinely unhinged right now. been trying to call arizona des for two weeks and either get the busy signal or get dropped after 45 mins

0 coins

Does Claimyr work for verification-specific issues or just general claim questions? Like would the agent they connect you to actually have access to fix the flag?

0 coins

Something I learned going through my own adjudication process last spring — when you get a live agent, the specific question you want to ask is what document code or hold code is currently on your claim file. Not 'why is my claim pending' because that gets a vague answer, but the actual code. That code will tell you exactly what triggered the review and what exactly needs to happen to clear it. Agents can see that in their system even when nothing shows on the claimant portal. I had a TC-4 hold that turned out to be a simple employer address mismatch and once I knew that, I could address it directly.

0 coins

Asking for the hold code specifically instead of just 'why is it pending' — that's actually really useful framing. I would have just asked the vague question and probably gotten nowhere.

0 coins

TC-4 from an employer address mismatch — I didn't realize they had specific codes for stuff like that. Good to know going into the call.

0 coins

This is solid advice. Generic questions get generic answers. The agents who actually want to help you need you to ask in a way they can look something up against.

0 coins

Seriously bookmarking this, I have a call attempt planned for tomorrow and I would have absolutely just asked the vague version.

0 coins

Letter in the mail dated three weeks ago is what finally clued me in — Arizona DES had sent a document request to an old address I hadn't updated after I moved. So while I was staring at the portal confused, there was a physical letter sitting undelivered. First thing to verify is that your mailing address in CACTUS is current. If you've moved in the last year, there's a decent chance a request went somewhere you're not.

0 coins

Moved about eight months ago and I honestly can't remember if I updated it in CACTUS specifically. Checking this immediately — that would explain everything.

0 coins

Address mismatch causing missed document requests happens constantly and Arizona DES still relies on physical mail for a lot of official requests which feels very 2005 but that's where we are.

0 coins

Day 31 of pending status is where I'm writing from. Filed in early March, construction layoff as well interestingly. Mine went into what they're calling 'manual review' according to the one agent I did manage to reach. She said it can take up to 45 days for manual review to complete which nearly gave me a heart attack but she also said I should keep filing weekly claims the whole time because if it approves, they'll pay out all the weeks at once retroactively.

0 coins

45 days for manual review — okay that's the scariest thing I've read today but the retroactive payment piece is at least some comfort. I have been keeping up with weekly claims so hopefully that holds.

0 coins

The retroactive payout part is true, that's standard. All your pending weeks pay out when the claim clears. The key really is not stopping your weekly certifications no matter how long it drags.

0 coins

i got so discouraged at week 5 i almost stopped filing. really glad i didn't because they did pay out all the back weeks when mine cleared

0 coins

Around the 3-week mark on mine I discovered that my employer had contested the claim, which I had no idea about. I thought I'd been let go because of project completion — which I had been — but my old company checked a box saying I'd quit voluntarily which is completely false. That's the kind of thing that sits in limbo forever because it goes into actual adjudication where both sides have to respond. Didn't show up anywhere on my portal as a flag, just looked like pending.

0 coins

An employer contesting the claim and calling a layoff a voluntary quit — that's a nightmare scenario I hadn't even considered. How did you even find out that's what happened?

0 coins

Only found out by getting an agent on the phone who could see the employer response in the file. Nothing on the portal indicated it. That's why calling is kind of unavoidable when pending stretches past a couple weeks.

0 coins

Employer contests are unfortunately more common than people realize, especially in project-based industries like construction. If that's what's happening, you'll need to respond to the adjudication with documentation showing the separation was employer-initiated — pay stubs, any written communication about the project end, anything like that.

0 coins

Two months from filing to first payment is my story — embarrassing how long it took but I finally got it resolved. Verification issue was the core of it and the way I cracked it was using Claimyr to get through to Arizona DES after weeks of failed calling attempts. The agent pulled up my file and found a flag I never would have known about from the portal. If you're in week four with no explanation, claimyr.com is worth trying, they also have a walkthrough video at https://youtu.be/vwA1GGuV83Y. Getting that live agent access changed everything for me.

0 coins

Two months is a long road but at least it resolved. The pattern here seems to be that actually getting a live agent is the only way to find out what the flag is — the portal just tells you nothing useful.

0 coins

Two months and it finally cleared — that actually gives me hope for my day 31 situation. What was the specific verification flag if you don't mind sharing?

0 coins

Day 31 to me sounds like you might be in the same manual review bucket I was in. Mine was an ID.me secondary verification that hadn't propagated to the DES system. Agent cleared it in about ten minutes once she found it.

0 coins

Week 7 when mine finally cleared and honestly the reason it took that long was me being too patient and not pushing harder earlier. The system is not going to fix itself or notify you proactively in most cases. You have to get aggressive about calling, sending messages through the portal, anything that creates a record and forces someone to look at your specific file.

0 coins

Week 7 and it only cleared because you pushed — that's the message I keep getting from this whole thread. I've been too passive waiting for them to fix it.

0 coins

Aggressive follow-up really does matter. Agents work a queue and claims that have recent contact or recent portal messages sometimes get priority review. Creating touchpoints isn't just useful psychologically, it can literally move your file.

0 coins

The 'send a message through the portal' approach also creates a paper trail which matters if you ever need to escalate or appeal anything.

0 coins

Middle of week two when I first noticed mine wasn't moving, hit week five before I had any answers. The thing nobody tells you upfront is that the job search requirement doesn't stop just because your claim is in pending or verification hold. You still have to log your three contacts per week and report them on your weekly certification. If your claim clears and they review your records and you weren't logging searches during the hold period, that can create a whole new problem.

0 coins

Still logging my three job search contacts every week even during this whole pending mess — glad I've been doing that right at least.

0 coins

Three contacts per week is the minimum and yeah you have to keep doing it even when it feels pointless because your claim is stuck. The requirements don't pause.

0 coins

I slacked on this during my adjudication because I figured why bother if it's all frozen anyway. Ended up being fine but definitely risky in hindsight.

0 coins

Something nobody mentioned yet — when you do get through to an agent, ask them specifically whether your claim is in 'adjudication' versus just a 'verification hold' because the path forward is totally different. Adjudication means there's an actual dispute or eligibility question being reviewed, and those have specific timelines and you have rights to respond with evidence. A verification hold is more administrative and usually clears once you provide whatever document they need. Got this explained to me after using Claimyr to reach Arizona DES — the agent walked me through the distinction and it completely changed how I handled my situation.

0 coins

Adjudication versus verification hold being two completely different tracks — I did not know this at all. I've been using those terms interchangeably in my head.

0 coins

This is an important distinction. Adjudication typically involves a formal process where you can submit evidence and sometimes even request a hearing if the determination goes against you. A verification hold is usually just a document or ID check that an agent can often clear on the spot.

0 coins

So basically if you're in adjudication you have more procedural rights but also more at stake, and if it's just a verification hold it should theoretically be faster to fix. Good to know which one you're dealing with before the call.

0 coins

Around week two of my pending experience I stopped waiting and started sending weekly messages through the CACTUS portal to Arizona DES directly. Not frantic messages, just factual ones — 'claim filed on X date, still pending, requesting status update and any required actions on my part.' Boring but professional. I think this contributed to my claim getting reviewed because by week four someone had actually responded and told me exactly what document was missing.

0 coins

The factual, professional tone in portal messages — I've been dreading writing them because I didn't know what to say but that's actually a good template.

0 coins

i sent one kind of emotional message early on and looking back that probably didn't help. factual and boring is probably the right move

0 coins

First letter from Arizona DES showed up in my mailbox at week three telling me they needed proof of my employment end date from my last employer. It was a simple form they needed my previous employer to sign. The annoying part was that my employer was slow to respond and that added another two weeks. If your employer is unresponsive, Arizona DES does have a process where you can submit alternative documentation like final pay stubs or a written statement — worth asking about.

0 coins

Alternative documentation if the employer is slow or unresponsive — that's really useful because I honestly can't guarantee my previous employer would respond quickly.

0 coins

Former employers dragging their feet on verification requests is super common and yes Arizona DES can usually work with alternate documentation if you explain the situation. Final paycheck stub plus any written communication about the layoff usually works.

0 coins

This happened to me and my employer never responded at all. Arizona DES ended up using my own documentation and it cleared eventually, just slower.

0 coins

About three weeks into pending is where I am right now reading this thread. My specific wrinkle is that I did gig work as a side thing while I was employed and I declared it correctly but I think Arizona DES might be reviewing whether my gig income affects my eligibility. Never had to navigate this before. Anyone dealt with the gig income piece specifically?

0 coins

The question to put to Arizona DES on that one is specifically whether your base period wages are calculated from W-2 employment only or whether the gig income is being factored into your eligibility threshold differently. The reason it matters is that gig income, if you were an independent contractor, is typically treated separately and shouldn't disqualify you from benefits earned through your regular W-2 job. But how you reported it can sometimes trigger a manual review flag.

0 coins

Gig income as a 1099 contractor should not affect your UI eligibility from your regular job, but the system sometimes flags it for review because it looks unusual. An agent can usually clear that up once they see the full picture of how you were employed.

0 coins

1099 gig income and W-2 regular job — good to know the distinction. I'll ask specifically about which wages are being looked at when I call.

0 coins

Week five currently. Tried calling Arizona DES 23 times over the last two weeks. That's not an exaggeration, I counted. Got through once, was on hold for 51 minutes, got disconnected without speaking to anyone. The calling situation is genuinely impossible right now and I'm starting to think there has to be a better way.

0 coins

23 times and one disconnect after 51 minutes is a level of phone misery I relate to deeply. the morning right when they open is slightly better but only slightly

0 coins

That was me a few months ago — until I tried Claimyr. Seriously, claimyr.com changed my relationship with the Arizona DES phone system completely. Instead of me sitting on hold, it monitors the lines and calls me when an agent is actually available. It's not magic but it beats 23 failed calls.

0 coins

Okay I'm looking at Claimyr right now. At this point I've got nothing to lose, week five with 23 failed calls is not a strategy.

0 coins

Month two of my claim, verification issue was the initial problem but it snowballed into an adjudication because Arizona DES couldn't confirm my last employer's business closure independently. Construction company had shut down operations in my area and there was no one to verify my separation with. Eventually resolved with a combination of my own documentation and a written declaration. Took forever but it did clear.

0 coins

Business closure with no one left to verify your separation — that's a really complicated version of this problem. Good to know that it can still resolve with your own documentation as the basis.

0 coins

Construction industry layoffs tied to business closures or project ends can be harder for Arizona DES to verify because there isn't always a clear employer response coming. Building a file of your own documentation from the start is smart.

0 coins

Just got off the phone with Arizona DES after week three of pending. Literally took all morning but I got through. They confirmed my claim has a 'secondary ID verification' flag specifically because my CACTUS account address doesn't match my ID.me address. Update your addresses in both systems to match exactly — same apartment number format, same abbreviations, everything. The agent said this mismatch is one of the most common reasons claims sit in verification without explanation.

0 coins

Address mismatch between CACTUS and ID.me causing a secondary verification flag — going to check both right now and make sure every single character matches.

0 coins

The 'same abbreviations' detail is key. St. versus Street, Apt versus Apt., minor formatting differences can apparently trigger a mismatch in their verification system. Worth being extremely specific when you update.

0 coins

I never would have thought to compare the two addresses character by character but this makes total sense given how automated these verification checks are.

0 coins

This is probably the most practically useful specific thing in this whole thread. Going to check my own CACTUS versus ID.me right now even though my claim is resolved just out of curiosity.

0 coins

Final update from me on a parallel situation — four weeks in pending, verification hold, used every trick in this thread and finally reached someone who could look at my actual file. The hold was because a digit in my SSN was apparently entered incorrectly somewhere in their system during initial filing, not by me but on their end. Something got transposed. Agent corrected it on the spot and my claim moved to payment processing within 48 hours. The lesson is you genuinely cannot know what the issue is until someone looks at the file — the portal will tell you nothing.

0 coins

A transposed digit in the SSN on their end — that's the kind of thing that would sit there forever without a human actually looking at the file. Really validates everyone saying you can't just wait for the portal to explain itself.

0 coins

48 hours from correction to payment processing is actually pretty fast once the actual issue is identified and cleared. The bottleneck really is just getting to the point where someone identifies the specific problem.

0 coins

Data entry errors on the agency side that then block your claim with no notification are genuinely one of the most frustrating outcomes because there's nothing you could have done to prevent it or catch it without calling.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure