My unemployment shows active issue with zero dollars — what does that even mean?
So I've been staring at my CACTUS portal for three days straight trying to figure out what's happening with my claim. I worked in commercial landscaping for about four years, got laid off six weeks ago when the company lost a major contract, filed my UI claim right away and everything seemed fine at first. Then I checked my payment history and it just shows $0.00 for every week even though my claim status says active. No letter in the mail explaining anything, no message in my portal inbox, nothing. I keep filing my weekly certifications on time and reporting my job search activities like I'm supposed to, but every single week just posts as zero dollars paid. I'm not in adjudication as far as I can tell — it doesn't say that anywhere. It literally just says active with a big fat zero next to every payment. Has anyone ever seen this before? What does it even mean when your unemployment shows active issue with zero dollars like that? I have rent due next week and I genuinely don't know what to do.
64 comments

Liam Fitzgerald
Your situation sounds almost identical to what happened with my claim back in February. Filed everything correctly, status showed active the whole time, weekly certs went through no problem — but every payment just sat at zero without any explanation attached to it. What ended up being the case for me was that there was an unresolved eligibility issue sitting on my account that never triggered an actual adjudication notice. DES sometimes has these internal flags that don't generate correspondence but still stop payments cold. Worth calling to ask them specifically whether there's an open issue code on your account, because the portal won't show you that detail directly.
0 coins
Amara Nnamani
Spent two weeks assuming mine was a portal glitch too. Turned out there was a flag on my account from a former employer who filed a discrepancy about my separation reason. Never got notified about it, just kept seeing zeroes. Calling in and asking about issue codes specifically is what finally got me an answer.
0 coins
Mei Lin
AuthorTwo weeks with no notice from DES about an employer dispute — that's exactly what I'm worried is happening here. My old employer wasn't happy about the layoff situation and I could see them trying to contest it. So I should specifically ask about issue codes when I call, not just claim status in general?
0 coins
Liam Fitzgerald
Yes, ask them to look at your claim for any open issue codes or holds that aren't reflected in your portal view. The rep can see way more detail on their end than what CACTUS shows you. Some of those flags are invisible to claimants until a human pulls up the account.
0 coins
Giovanni Mancini
The zero dollar active status thing tripped me up for about a month before I understood what was going on. What finally made it click for me: active just means your claim exists and hasn't been closed, it doesn't mean payments are cleared to go out. The dollar amount showing zero while active usually points to either a base period wage calculation issue or an open eligibility question that stopped the payment queue without formally moving the claim into adjudication status. For the wage calculation angle — do you know roughly what your quarterly earnings looked like in the year before you filed? If your highest earning quarter was under a certain threshold the system might have calculated a zero benefit amount, which would explain everything you're seeing without any flag or issue code at all.
0 coins
Mei Lin
AuthorMade about $47,000 last year total so wages shouldn't be the problem I think. I was full time the whole time. But I hadn't even thought about the distinction between active and payment-cleared — that's a really useful way to think about it.
0 coins
NebulaNinja
Same thing bit me last year. Active status felt like confirmation everything was fine but those two things actually mean completely different things in the DES system. My payments were stuck because of a discrepancy in how my employer reported one quarter of wages and my claim just sat there looking normal while nothing paid out.
0 coins
Giovanni Mancini
With $47k in annual wages your benefit amount calculation should be nowhere near zero, so that rules out the base period problem. That shifts it back toward some kind of eligibility hold or employer dispute on the account. Those are almost always invisible in the portal but very fixable once you get someone on the phone who can actually see your file.
0 coins
Fatima Al-Suwaidi
When my claim showed that same zero pattern for three weeks I tried everything — online messages, the portal chat, leaving voicemails — and nothing got me any closer to an actual answer. A friend told me to try Claimyr at claimyr.com because she'd used it when her adjudication dragged on for two months. It basically handles the hold queue for you so you end up connected to a live DES agent without spending your whole day redialing. There's a demo video at https://youtu.be/vwA1GGuV83Y that shows how it works if you want to see it before trying it. For me the difference was talking to an agent who could actually see the issue code on my account versus just reading my portal page over and over and guessing.
0 coins
Dylan Mitchell
Burned through almost four hours one morning trying to get through to DES on my own, kept hitting the high-volume message and getting disconnected. Eventually caved and tried something similar. Having an actual agent pull up your file is completely different from anything the portal gives you — they can see hold codes, employer responses, internal notes, all of it.
0 coins
Mei Lin
AuthorThe hold queue is what kills me every time I try calling. I'll keep the Claimyr info, especially since it sounds like whatever is wrong with my account is only going to be visible to an agent anyway. At this point I'd rather not wait another week hoping the portal updates.
0 coins
Sofia Morales
Not sure I'd pay for a service to call a government agency but I get it when you're desperate and rent is coming. If the issue is an employer dispute the clock matters because those have response deadlines and if DES makes a determination while you're still trying to figure out what's even happening it gets harder to fix retroactively.
0 coins
Dmitry Popov
Something that doesn't get talked about enough in these threads: when your weekly certification goes through and shows as processed but the payment amount is zero, that specific combination usually means the claim passed the certification check but got blocked at the payment authorization step. That's different from a certification error. The block at payment authorization almost always traces back to either an employer wage dispute, a separation reason question that never formally opened, or a secondary eligibility flag like able and available status being questioned. None of those show up in your claimant portal as a separate status — they're just internal holds.
0 coins
Ava Garcia
The separation reason question being invisible was exactly what happened on my claim. My former employer checked a different termination code than what I reported and that created a discrepancy that blocked payments without ever showing me any notice. I didn't find out until I finally reached someone by phone.
0 coins
Mei Lin
AuthorSo my certifications are literally going through fine but then hitting a wall right before the actual payment releases. That makes the zero dollars make a lot more sense. It's not that I'm doing anything wrong in the weekly filing — something is sitting upstream of that.
0 coins
Dmitry Popov
Exactly right. Your certifications are probably perfectly fine. The hold is upstream of that final step. Which means no amount of refiling or adjusting your certification is going to fix it — you need someone at DES to remove whatever flag is sitting on the payment authorization side of your account.
0 coins
StarSailor}
I want to push back a little on the idea that this is definitely an employer dispute. When my claim showed active with zeroes for about five weeks the reason turned out to be completely different — my identity verification had stalled in the ID.me process even though the portal showed my account as active. DES had not sent me any notice about it and my certifications were still being accepted. The ID.me verification step and the claim active status are tracked separately in their system, so a half-verified identity can let your claim activate while still blocking payments at the back end.
0 coins
Miguel Silva
ID.me stuff causing invisible payment blocks is super underreported. Mine looked exactly the same — active claim, accepted certifications, zero dollars paid, no explanation anywhere. Turned out there was a step in my ID.me verification that showed complete on my end but had a pending flag on DES's side that I had no way of seeing.
0 coins
Mei Lin
AuthorGenuinely hadn't thought about ID.me being part of this. I went through the verification when I first set up the account but maybe there was a step that didn't fully complete on the DES side even though it looked done from my end. How did you find out that was the issue — did you have to call DES or was it something you could resolve through ID.me directly?
0 coins
StarSailor}
Had to call DES to find out it was the ID.me flag specifically, then they directed me to fix it through ID.me's support. DES couldn't fix it on their end, but they could at least tell me what the hold was and confirm that clearing the ID.me issue would release the payment queue.
0 coins
Zainab Ismail
Three different things can cause the exact issue you're describing and they look completely identical from the claimant's side. What separates them is what your employer reported, what quarter your earnings peak fell in, and when exactly you filed relative to your last day of work. If your last paycheck crossed into a new calendar quarter right before you filed, your base period might have a gap that the system flagged automatically even if your total wages look fine. That quarterly boundary thing is surprisingly common and almost never explained in anything DES sends claimants.
0 coins
Connor O'Neill
My last day at work was December 31st and I filed in early January thinking I'd have a full year of wages behind me. Turned out the way the base period works meant one of my strongest earning quarters barely counted, and my calculated benefit amount was way lower than expected. Not zero in my case but I could see how the timing could push someone to zero depending on how wages were distributed.
0 coins
Mei Lin
AuthorMy layoff was effective the last week of March and I filed the first week of April. I honestly don't know if that timing matters but based on what you're saying that could actually be relevant to whatever is flagged on my account.
0 coins
Zainab Ismail
That March-April cutoff is exactly the kind of timing that sometimes creates a base period complication. Arizona DES uses your earnings from roughly the first four of the last five completed calendar quarters. Depending on how your wages were distributed across quarters, a late-March separation could mean your most recent strong quarter doesn't count the way you'd expect. This is worth asking about specifically when you reach an agent.
0 coins
Yara Nassar
Jumped into this thread because the same exact thing happened to my partner last month and I want to share what finally resolved it. Her claim was active, certifications accepted every week, zero dollars paid for almost a month. When she finally got through to DES they found two separate issues stacked on her account — an employer dispute that had been filed and a secondary flag from a system mismatch between her reported wages and what her employer submitted in their quarterly filings. Neither of those had generated any notice. Both got resolved in the same call once an agent actually looked at the account.
0 coins
Keisha Robinson
Two stacked issues is brutal because even if you figure out one of them the other one keeps blocking payments and you have no idea. My situation was similar — I resolved what I thought was the only problem and then nothing changed, and I had to call back and find out there was a second unrelated hold that the first agent hadn't mentioned.
0 coins
Mei Lin
AuthorTwo separate flags on one account with no notice for either one — I really hope that's not what I'm dealing with but it's starting to sound possible. At least knowing they can resolve both in one call if the agent actually looks at the full account is reassuring.
0 coins
Yara Nassar
Ask them specifically to do a full account review not just check the top-level status. The rep who resolved both of my partner's issues said she explicitly looked through every open item on the account rather than just addressing whatever the first thing that came up was. That's apparently not always standard procedure.
0 coins
Giovanni Mancini
Since we're talking about getting DES on the phone — this is the part that matters for the zero dollar situation specifically. Any employer dispute on your claim has a response deadline, and if DES makes a default determination while you're still in the phone queue trying to find out what's happening, that determination can go against you even if you would have had a solid case. The window to respond is usually 10 days from when DES issued the question to your employer, not from when you find out about it. If there's an employer dispute on your account right now that you don't know about, time is working against you.
0 coins
GalaxyGuardian
The 10-day window thing is real and I found out the hard way. My employer filed a dispute and I had no idea it existed. By the time I reached anyone at DES to find out what was blocking my payments, the response window had already passed and there was a preliminary determination on file that I then had to appeal formally instead of just responding to the original question. Claimyr was actually what finally got me to an agent fast enough to understand what was happening — once I used it at claimyr.com the whole situation became clear within about 20 minutes of being on the phone with someone.
0 coins
Mei Lin
AuthorThe 10-day clock running without me knowing about it is the most stressful thing I've read in this thread. I've already been sitting on this zero dollar situation for almost three weeks. If there's a dispute I need to know about it immediately.
0 coins
Paolo Ricci
The timeline pressure is real and I'd been in a similar spot — three weeks of zeroes and then found out through Claimyr that there was an employer response already on file that I hadn't been notified about. The agent I spoke to was able to look at the full timeline and explain exactly where things stood. At least I knew what I was dealing with instead of just watching zeroes accumulate.
0 coins
Amina Toure
Something practical you can do right now without calling: log into your CACTUS portal and look at your payment history detail, not just the summary view. Each week should have a status code attached to it, and those codes sometimes give you a clue even if they're not explained anywhere obvious. Codes that start with certain letters indicate employer-related holds while others indicate identity or wage verification holds. It's not a full answer but it might narrow down which direction your problem is pointing before you get through to an agent.
0 coins
Mei Lin
AuthorWent back and looked at the detail view just now — every week shows a code I haven't seen explained anywhere in the portal documentation. It's not adjudication, it's not a standard hold code from the FAQ. That actually tells me something, even if I don't know exactly what it means yet.
0 coins
Amara Nnamani
The undocumented codes are a real thing. DES portal shows claimants a subset of the status information with no key to decode it. Some of those codes are only explained in internal documentation that reps have access to. Worth writing down the exact code you're seeing and then asking the agent what it means when you call.
0 coins
Amina Toure
Write down that code before you call and read it back to the agent word for word. Sometimes just saying 'I see code XYZ on every week in my payment history' prompts them to look at exactly the right part of your file immediately instead of doing a general status check that might not surface the real issue.
0 coins
Ava Garcia
Want to add one thing that hasn't come up yet. If your situation does turn out to be an employer dispute, the resolution process depends a lot on what reason your employer gave for the separation versus what you reported. Laid off because a company lost a contract is about as clean a separation reason as you can have — that's clearly not a voluntary quit and not misconduct. But if your employer reported something different, even a slight difference in how they characterized the ending of employment, that can create an eligibility question that freezes payments while DES figures out whose account matches reality. The fix for that is usually just submitting documentation of the actual separation circumstances.
0 coins
Mei Lin
AuthorMy separation documentation should be solid — the layoff was company-wide, there were multiple people let go at the same time, and it was directly tied to the contract loss which was public information in our industry. If they filed something contradictory that would genuinely surprise me but I guess it happens.
0 coins
Liam Fitzgerald
Even well-documented mass layoffs sometimes generate disputes because employers respond to DES questionnaires in bulk and sometimes check the wrong box for individual employees. It's not always intentional but it creates the same payment freeze either way. Good separation documentation puts you in a strong position once you actually get to explain the situation to someone.
0 coins
Ava Garcia
The contract loss documentation is a strong card to have. If you can show any company communications about the layoff — email announcing it, anything mentioning the contract situation — that kind of contemporaneous documentation carries a lot of weight in resolving separation disputes quickly.
0 coins
Oliver Zimmermann
Jumped in because I work adjacent to HR and see the DES employer response side of things sometimes. When a company submits their response to a DES separation inquiry they're often filling out a form that doesn't have a lot of nuance in the answer options. A layoff due to business reasons and an end of project completion and a contract non-renewal all get funneled into similar checkbox categories, and sometimes the checkbox an HR person clicks in a hurry doesn't match what actually happened with enough precision for DES to automatically clear the claim. It's not always the employer trying to fight your claim — sometimes it's just a form filed sloppily.
0 coins
Dylan Mitchell
Sloppy form filing causing a month of zero dollars and no notice is somehow even more frustrating than intentional disputes. At least if the employer is actively fighting it there's a clear adversary. A checkbox someone didn't think about carefully is infuriating.
0 coins
Mei Lin
AuthorHonestly that tracks with what I know about how my former employer operates. HR was always overwhelmed and doing things in bulk. I can absolutely see a scenario where someone filled out the DES response form in five minutes without really thinking about how their answer would affect individual claims.
0 coins
Oliver Zimmermann
When you get to an agent and they tell you there's an employer response issue, ask them whether it looks like a simple categorization mismatch versus an active dispute. Those two things go through different resolution tracks. A categorization mismatch with solid documentation on your side usually resolves much faster than a contested separation claim.
0 coins
Sofia Morales
Have to mention something nobody has said directly yet. When your claim finally does get corrected and payments release, they should be retroactive for all the weeks you certified correctly during the hold period. You won't lose those weeks just because they showed zero while the issue was unresolved. As long as your certifications are on record — which yours are — the back payments should come through once the hold is cleared. This is assuming the resolution goes in your favor on whatever the underlying issue is.
0 coins
Keisha Robinson
This was huge for me when I finally got my hold cleared. Four weeks of zeroes became four weeks of back payments hitting my account within about two business days after the resolution. Keep filing your certifications every week regardless of what the payment shows, because those certified weeks are what determines your retroactive amount.
0 coins
Mei Lin
AuthorKnowing those zeroed weeks should convert to back payments once this gets resolved takes a little pressure off. I'll keep filing every week. At this point I just need to understand what I'm fighting and get in front of an actual person at DES who can fix it.
0 coins
Sofia Morales
Keep records of every certification you file, including the date and any confirmation number the portal gives you. If there's ever any question about which weeks are owed on the back payment, having that documentation makes the conversation much simpler.
0 coins
NebulaNinja
Just want to validate something for everyone who's been reading this thread: the portal really does hide critical information from claimants in a way that seems almost designed to prevent people from advocating for themselves. When I had my hold issue I called four times and got agents who just read me my portal status back as if that was helpful. The fifth call I finally got someone who actually dug into the account notes and found two separate issue codes that none of the previous agents had mentioned. Same system, same account, completely different information depending on who you get.
0 coins
Connor O'Neill
The lottery of which agent you get is the most maddening part. I had one agent tell me my claim looked completely fine and would probably update on its own, then called back two days later and got someone who immediately found an employer dispute that had been sitting there for three weeks. Same claim, same day basically.
0 coins
Mei Lin
AuthorFour calls that just read back the portal and then one that actually found the problem — that's exactly the experience I've been having and dreading. How do I make sure I get someone who will actually dig in versus someone who's just going to tell me my status is active?
0 coins
NebulaNinja
Ask for a full account review and specifically say you need them to look at any open issue or hold codes, not just the claim status. If the agent you get seems to be just reciting portal info back to you, ask them directly whether there are any internal notes or codes on your account beyond what the portal shows. Some agents respond to that by actually looking deeper.
0 coins
Miguel Silva
The ID.me angle from earlier in the thread is worth revisiting because there's a specific scenario that's really common and not well documented anywhere. If you completed your ID.me verification on a mobile browser and then accessed your DES account from a desktop later, there's sometimes a device verification mismatch that creates a secondary identity hold on the payment side even though your overall account shows as verified. DES and ID.me both show your account as fine but there's a linking issue between them that blocks payment release.
0 coins
Dylan Mitchell
Had the mobile-to-desktop mismatch issue. Everything showed verified, everything showed active, payments zero. The fix was going back through ID.me verification specifically on the same device and browser type I was going to use going forward for DES access, then waiting about 48 hours for the systems to sync. Frustratingly simple once you know about it, completely invisible before that.
0 coins
Mei Lin
AuthorI did my initial setup on my phone and have been checking the portal mostly on my laptop since then. That could genuinely be contributing to whatever is going on. I'll try re-verifying through ID.me on my laptop and see if anything changes in the next 48 hours while I'm also working on getting through to an agent.
0 coins
Miguel Silva
Give it the full 48 hours before assuming it didn't work — the sync between ID.me and DES is not instant and sometimes takes the full two days. If you're at the 48 hour mark with no change then the ID.me mismatch probably isn't the whole issue and you're back to needing a live agent to find the actual hold code.
0 coins
Oliver Zimmermann
Circling back to the original question because I think it's worth stating clearly after all these responses: unemployment shows active issue with zero dollars is not a normal or expected state for a claim. Active and paying zero are fundamentally incompatible unless something is specifically blocking payment on the back end. The system isn't designed to show active claims with zero payments unless a flag or hold exists somewhere in the payment authorization chain. So whatever anyone tells you about waiting it out or assuming it's a glitch — it isn't. Something specific is wrong and something specific needs to be fixed.
0 coins
Amara Nnamani
Wish someone had told me this directly instead of letting me assume it would self-correct. Spent two weeks refreshing my portal thinking the system would catch up. The hold doesn't go away on its own — it requires either a DES agent action or a resolution of whatever underlying question triggered it.
0 coins
Mei Lin
AuthorThis is the clearest framing of what's happening that I've seen in this whole thread and it's honestly what I needed to hear. It's not ambiguous, it's not a glitch, something is specifically blocking my payments and I need to get it fixed rather than waiting.
0 coins
Amina Toure
The waiting-it-out instinct is understandable because sometimes DES issues do self-resolve, but the zero dollar active combination specifically is different. That one needs active intervention. Document what you know so far and get to an agent with that detail — it'll make the call more productive.
0 coins
StarSailor}
One last practical piece: when you do get through to an agent, start the call by saying you have an active claim with zero dollars showing on all your payment weeks and you need to know what specific hold or issue code is preventing payment authorization. That framing tells the agent immediately that you've already looked at your portal, you know the basic status isn't the question, and you need them to look deeper. Agents respond differently to callers who come in with specific technical questions versus callers who just say they haven't been paid.
0 coins
Connor O'Neill
Coming in with the specific framing made a real difference on my call. The agent who finally resolved my issue told me I was clearly familiar with how the system worked and that made her take my call more seriously. She spent longer on my account than she might have otherwise.
0 coins
Keisha Robinson
Wrote down almost exactly that script before my call and it worked well. The agent went straight to the issue codes view instead of walking through the basic status checks that every other agent had started with. Specific technical framing signals to them that you won't be satisfied with a surface-level answer.
0 coins
Mei Lin
AuthorGoing into the call prepared with what I know and what I need them to look for specifically feels like a much better approach than just saying I haven't received any payments. Thank you for this — along with everything else in this thread I finally feel like I understand what's going on and have a real plan to fix it.
0 coins