Back to Arizona Unemployment

Logan Chiang

How to fix active issues on unemployment claim with Arizona DES

So I'm sitting here staring at my CACTUS portal and there's this 'active issue' flag on my claim that showed up out of nowhere after my third week of certifying. No letter, no explanation, nothing in my inbox telling me what triggered it. I was laid off from my logistics coordinator job about six weeks ago, got approved pretty quickly at first, received two payments without problems, and then week three just... stopped. The portal shows my weekly certifications are submitted but there's this issue sitting there blocking everything. I work part-time gigs occasionally through a staffing agency and I did report those hours correctly during my weekly claim - I listed every shift, every dollar. So I genuinely don't know if that's what flagged it or if it's something else entirely. My job search log is current, I've been applying to at least three positions a week like required, and I even attended an ARIZONA@WORK orientation. Everything I can think to check on my end looks fine. Called Arizona DES probably nine times over two weeks. Twice I got the automated system hang-up before I even reached a queue. Three times I waited over an hour and got disconnected. The other four times I couldn't even get into the hold queue because they said call volume was too high. I have no idea how to fix active issues on unemployment claim and get this resolved. Anyone dealt with this and actually gotten through to someone?

Week four of my own adjudication mess here, so I feel this deeply. The 'active issue' label in CACTUS is genuinely one of the most frustrating things about the Arizona DES system because it tells you something is wrong without telling you what. From what I went through, the most common triggers are: unreported or misreported wages, a former employer disputing your separation reason, identity verification flags, or sometimes just a system hiccup when part-time work income gets calculated. Since you're doing staffing agency shifts, I'd almost bet it's an income reconciliation flag - the agency reports your wages to Arizona DES on their own schedule and sometimes what you report on your weekly claim and what they report to the state don't match to the penny, even when you did everything right. The fix requires an adjudicator to manually review and clear it, which is why you absolutely have to get a live person on the phone. There's no portal button to resolve this yourself.

0 coins

By week four I'll be completely broke so that's not comforting lol. The staffing agency theory makes a lot of sense though - their pay periods run biweekly but I certify weekly so there's probably a timing mismatch. How did you eventually get someone on the phone to clear yours?

0 coins

Not sure the staffing agency timing is always the culprit - mine got flagged with an active issue and I had zero part-time work at all, just a straightforward layoff. Sometimes it really is just a system thing.

0 coins

That's a fair point, I was going off my own situation. The income mismatch is common but definitely not the only cause. Bottom line is that regardless of why the flag appeared, getting it cleared requires the same thing: talking to an actual adjudicator.

0 coins

Three weeks into having a similar active issue on my claim when I finally got through to Arizona DES, and the thing that actually worked for me was using Claimyr. I'd been doing the same thing you're doing - calling over and over, getting disconnected, hearing 'call volume too high' on repeat. Someone in a different thread mentioned Claimyr and I was skeptical but desperate enough to try it. It basically handles getting into the Arizona DES phone queue for you and calls you back when an agent is on the line. Took way less time than any of my own attempts. The agent I spoke with was able to look at my active issue flag right away and explain exactly what was causing it. You can check it out at claimyr.com - there's also a video showing how it works at https://youtu.be/vwA1GGuV83Y if you want to see before you try it.

0 coins

Okay this is actually the most useful thing I've read today. I've been burning hours on hold with nothing to show for it. Going to look at that video right now.

0 coins

Second full week with my issue flag here and just bookmarked claimyr.com after reading this. The call situation is genuinely impossible right now.

0 coins

does this actually work or is it just another thing that sounds good but doesnt deliver

0 coins

Worked for me personally, that's all I can say. I was at the point where I'd tried everything else so I had nothing to lose by trying it.

0 coins

Fifth week of certifying here and I actually had an active issue clear on its own after about 10 days, so that's one data point. But I wouldn't count on that being typical. Mine was apparently a minor employer record mismatch that the system auto-resolved. If yours involves actual wage verification or a separation dispute, those don't auto-clear - an adjudicator has to touch your file. The portal won't update you either, you just have to keep checking back or get someone on the phone.

0 coins

Not sure waiting 10 days is advice I'd give someone whose bills are due, though. The auto-clear thing is real but it's honestly a gamble.

0 coins

Mine has already been sitting there almost two weeks with zero movement so I think I'm past the auto-clear window unfortunately.

0 coins

auto clear happened to me too but it took 3 weeks and i almost had a heart attack every time i checked the portal

0 coins

Yeah three weeks would have broken me. Mine clearing at 10 days felt like luck, not a system working properly.

0 coins

Just got my active issue resolved yesterday after six weeks of fighting it. What finally worked was a combination of things - I used Claimyr to actually get through to Arizona DES (same experience as the person above, the regular calling route was completely useless), and when I finally had an agent on the line I had everything ready: my separation letter from my employer, my pay stubs for the weeks in question, and a written timeline of when I reported what earnings. The agent told me having documentation ready made the call go much faster because they didn't have to put me on hold to verify things manually. If you're going to try to reach them, go in prepared.

0 coins

Six weeks is a long time to have payments frozen. I'm making a folder tonight with everything - separation paperwork, all my pay stubs, the weekly certification records I screenshot every time I submit. What number did you call when you used Claimyr, is it the main Arizona DES UI line?

0 coins

The documentation tip is genuinely important - I went into my call without anything pulled up and the agent had to put me on hold twice to look up info I should have just had ready.

0 coins

Exactly. They're looking at your file on their end but if you can confirm dates and amounts quickly it speeds the whole thing up. The agents seem genuinely more engaged when the caller is organized.

0 coins

what documentation did they actually need, like original employer docs or is a printed screenshot enough

0 coins

Agent I spoke with accepted screenshots of my CACTUS portal history and my bank deposits as confirmation of timing. I think what matters most is that you can show your version of events clearly, not that it's on official letterhead.

0 coins

My claim had an active issue last year and I want to clear up something I see people get confused about - an active issue and an adjudication hold are related but not exactly the same thing. An active issue is the flag that appears in CACTUS indicating something needs review. Adjudication is the actual review process that happens after the flag is created. I spent two weeks thinking my claim was 'in adjudication' when really it was flagged but hadn't been assigned to an adjudicator yet - that's a different queue and a different wait time. When I finally got through on the phone, the agent explained that my flag existed but was sitting unassigned, which is apparently common during high-volume periods. Getting an agent to manually assign your case can actually speed things up significantly.

0 coins

Wait, so there's a difference between a flag sitting there and it actually being reviewed? That would explain why mine hasn't moved. I assumed someone was at least looking at it.

0 coins

This distinction genuinely confused me for weeks. I kept telling people my claim was 'in adjudication' and then an agent told me it hadn't been picked up yet.

0 coins

It's a confusing setup honestly. The portal shows the same 'active issue' status whether it's assigned or not, which gives people no useful information about where they actually are in the process.

0 coins

My employer contested my separation and I went through almost exactly this - flag appeared, nothing moved for weeks, turns out nobody had been assigned to actually review it yet. Once a human assigned it, it was resolved in four days.

0 coins

Just starting week two with my active issue flag and reading this thread has me stressed. Quick question - do you have to keep submitting your weekly certifications even when there's an active issue blocking payment? I stopped after the second week thinking there was no point.

0 coins

Keep certifying every single week without exception. This is really important - if you stop certifying while your issue is pending and it eventually gets resolved, Arizona DES may not pay you back for the weeks you didn't certify. You have to maintain your claim actively the whole time even if no money is coming in.

0 coins

Okay glad I asked because I almost let this week lapse. Submitting right now.

0 coins

Definitely keep certifying - I made the mistake of stopping after three weeks of no payment during my own active issue. When it cleared, I had to call Arizona DES to explain the gap and request backdating, which added more weeks to the whole process. Really not worth it.

0 coins

The backdating process sounds like a nightmare. Definitely not stopping my weekly claims again regardless of what the portal shows.

0 coins

Eight days into having my active issue appear, and honestly the phone situation was what broke me first. I'd been trying the main Arizona DES line for days. Someone at my ARIZONA@WORK appointment mentioned Claimyr as a way to get through without spending your whole day redialing. I tried it and got a callback with an agent within a reasonable time - way better than my previous attempts. The agent actually walked me through what was causing my flag (turned out to be an employer record discrepancy, not anything I did wrong) and started the process to clear it on the call. The claimyr.com site has the info if you want to check it out.

0 coins

The employer record discrepancy thing - my previous employer misspelled my name slightly in their reporting and that was apparently enough to trigger a flag on my claim. Completely outside my control.

0 coins

Same kind of thing for me. The agent said these employer-side errors are more common than people think and they're some of the faster ones to clear once an adjudicator actually looks at the file.

0 coins

Someone at ARIZONA@WORK mentioned it? I have an appointment there next week - good to know people on the ground are aware of it as an option.

0 coins

My situation was a little different but I think relevant - I had an active issue appear because I didn't correctly understand what 'available for work' meant during a week I had a scheduled medical procedure. I answered the weekly certification question wrong basically. What I didn't know at the time was that Arizona DES has specific rules about temporary unavailability - a one-day medical appointment doesn't necessarily disqualify you for the whole week but I'd answered the question as if I was completely unavailable. When I finally got through to an adjudicator they explained the distinction and walked back my answer. If anyone answered their weekly cert questions without fully understanding what the question was actually asking, that could be triggering flags you don't even realize are coming.

0 coins

The weekly certification questions are genuinely ambiguous in a few places. 'Available for work' doesn't mean the same thing in common language as it does in Arizona DES definitions.

0 coins

I've been answering mine carefully but now I'm second-guessing every question I've ever submitted. Hopefully my answers were right.

0 coins

Don't panic retroactively - if your answers were submitted in good faith based on your understanding, that works in your favor when talking to an adjudicator. What matters is being honest, not perfect.

0 coins

the available for work question tripped me up too, specifically around a week I had a job interview that required travel. I wasn't sure if 'available' meant I had to be physically near my home or just willing to accept work

0 coins

Final update from someone who just got through this whole process last week - the active issue on my claim took 31 days total to resolve. Here's what I actually learned: the first two weeks I did nothing useful because I couldn't reach anyone. Around day 15 I started using Claimyr to handle the hold queue, which is how I finally got an agent on the line. Turned out my active issue was a wage verification flag because one of my staffing agency shifts overlapped with an old part-time employer's quarterly wage report to the state. The adjudicator reconciled the records and cleared it on the call, then told me to expect payment within 3-5 business days for all the held weeks. Got paid four days later. If you're in this situation right now, getting a live Arizona DES agent on the phone is the only real path forward - everything else is just waiting and hoping.

0 coins

31 days and you got all back pay? That's actually better than I feared. I was worried they'd deny the held weeks entirely. This gives me some hope.

0 coins

The quarterly wage report overlap thing - that's exactly what happened to mine. The timing between how staffing agencies report and how often DES checks those records creates these mismatches even when the claimant did everything correctly.

0 coins

Exactly. And the frustrating part is there's no way to know that's what triggered it until you actually talk to someone. The portal just shows the flag with no context.

0 coins

back pay for all held weeks is something I genuinely didn't know was possible. My active issue just appeared and I was assuming that money was gone.

0 coins

Don't assume it's gone. When an active issue is cleared and it's determined you were eligible, Arizona DES typically releases all the held weekly payments. That's why keeping up with weekly certifications during the hold matters so much.

0 coins

Just realized something that might help people here - when you call Arizona DES and reach an agent about an active issue, ask them specifically to tell you the issue TYPE and the date it was created. A lot of people (including me initially) just ask 'what's going on with my claim' and get vague answers. When you ask for the specific issue type code and creation date, the conversation gets more concrete immediately. The agent I spoke with gave me the exact reason code and I was able to look it up and understand exactly what documentation I needed before calling back for the resolution step.

0 coins

Issue type code - I never would have thought to ask for that specifically. Adding it to my list of things to ask when I get through.

0 coins

My first call I just said 'I have an active issue' and the agent gave me very generic information. Second call when I asked for the specific code things got much more useful immediately.

0 coins

The specificity thing really does change how the call goes. Agents seem to shift into a more concrete mode when you're asking specific procedural questions rather than general ones.

0 coins

What do you do with the reason code once you have it? Is there somewhere on the Arizona DES site that explains what each one means?

0 coins

Honestly I just searched the code plus 'Arizona DES' and found enough to understand it. There's no official public glossary that I found but the codes are specific enough that you can usually figure out what documentation will help resolve them.

0 coins

Okay I want to push back a little on the 'just call them' advice - I know everyone here is saying call, call, call, but what about the portal message system? Has anyone actually had any success resolving an active issue through the CACTUS portal messaging rather than by phone? I've sent three messages in the last two weeks and gotten nothing back but I'm wondering if I'm doing it wrong or just unlucky.

0 coins

Not to dismiss the portal messages entirely, but in my experience and from what I've read on this forum, active issue flags on Arizona DES claims almost always require a phone call to resolve. The portal messages go to a general inbox and may not get routed to whoever is handling your specific adjudication. Phone calls get you to someone who can actually access and modify your file in real time.

0 coins

Ugh. I was really hoping the portal would be a viable option. Phone anxiety is real and spending hours redialing is genuinely difficult for me.

0 coins

That's completely understandable. If the redialing is the hard part, the Claimyr approach others mentioned in this thread might actually be a good fit - it removes the repetitive dialing and waiting part specifically.

0 coins

Sent portal messages for 10 days during my active issue period and heard nothing. Phone call resolved it same day. The messages might eventually get a response but I wouldn't count on them for anything time-sensitive.

0 coins

My situation going into week three and I keep reading that people are reporting part-time wages 'correctly' but I realized I might have been making a mistake without knowing. When you have a part-time shift that crosses midnight - like working 10pm to 2am - do you report all those hours under the day the shift started or the day it ended? I've been reporting them all as the day I started the shift but now I'm worried I've been doing it wrong and that's why my claim got flagged.

0 coins

My understanding is that for the weekly certification, what matters is which benefit week the earnings fall in, not the specific day within that week. The midnight crossing is usually only an issue if the hours span across the weekly certification boundary (Sunday midnight in Arizona). But honestly this is specific enough that you should confirm with an Arizona DES agent rather than taking my word for it.

0 coins

The weekly boundary is the thing I hadn't thought about. Most of my shifts are mid-week so probably fine but I'm definitely going to confirm this.

0 coins

the midnight shift thing never even occurred to me and i've been doing this for four months. probably should double-check my own records now

0 coins

Coming at this from a different angle - I had an active issue that turned out to be an identity verification flag, not anything wage-related. This apparently happens sometimes when Arizona DES systems flag inconsistencies in your personal information during ID.me verification. The process to resolve it was different from a wage dispute - they needed me to do a secondary ID verification through the portal and then call to confirm it was completed. Took about two weeks total. Just want people to know the 'active issue' category can mean a lot of different things.

0 coins

ID verification - I went through the ID.me process when I first filed and thought that was done. Is there a way to check if that's the type of issue you have without calling?

0 coins

In my case the portal had a subtle notification about a 'verification step required' buried under my claim details, not prominently flagged. Worth looking carefully at every section of your CACTUS account, not just the main status banner.

0 coins

Going to dig through every corner of the portal tonight. I honestly might have missed something like that.

0 coins

ID verification flags are incredibly frustrating because there's no obvious reason for them - everything looks correct to you but the system sees something it doesn't like in the records. Mine cleared after I re-uploaded my documents through the portal.

0 coins

Fourteen days after my active issue first appeared, I want to share what the adjudicator actually told me when I finally got through. She said the number one thing people do wrong is wait too long hoping the flag resolves on its own, and the number two thing is calling without documentation. She also said that when you call, you should ask to have a note added to your file confirming the date and content of the conversation - that way if something gets lost or reassigned, there's a record that you were proactive. That note-requesting tip I had never heard before and it made my second call much smoother because the first agent had logged our conversation.

0 coins

Asking them to log the conversation is really smart. I wish I'd known that at the start of my situation - I had a call where an agent told me one thing and then a later agent said the opposite, and there was no record of what the first person said.

0 coins

The 'ask to have a note added' tip is going in my call prep list right now. That's the kind of thing you don't know to ask until someone tells you.

0 coins

Exactly why I shared it. The adjudicators and agents are generally helpful once you reach them - the system is what's frustrating, not usually the people.

0 coins

Documentation of calls is something that feels obvious in retrospect but I never thought to do it. I've been calling and not writing down who I spoke to, what they said, or what they said would happen next.

0 coins

My first week of certifying after a layoff I had no idea what I was doing and I answered some questions on autopilot without reading them carefully. That carelessness is what eventually caught up with me - around week five an active issue appeared that turned out to trace back to an inconsistency in how I'd answered a separation question in week one versus how my employer characterized my departure. The rule I didn't know: your answers have to stay consistent across all your certifications, and if your former employer submits something different from what you stated, that creates a flag that an adjudicator has to reconcile. So if anything you answered early in your claim process was rushed or unclear, that might be what's surfacing now.

0 coins

Week one I was definitely stressed and not paying full attention to every question. The separation question is one I might have answered too quickly.

0 coins

This happened to my coworker who was laid off at the same time as me - her answers were fine but her manager submitted a different reason for the separation and she spent weeks dealing with the flag it created.

0 coins

Employer-submitted separation reasons are a really common trigger that people don't see coming because they had no control over what the employer filed. It's not about anything the claimant did wrong.

0 coins

The consistency point is important - even if your answers were technically accurate, if week one and week three describe your situation differently, the system flags it even without employer input.

0 coins

Something nobody has mentioned yet - the Arizona DES website has a 'schedule a callback' feature during certain hours that is theoretically an alternative to sitting on hold. I tried it twice. First time they never called back. Second time they called back at an inconvenient time and I missed it. I'm not saying don't try it, but don't rely on it as your primary strategy if you're trying to resolve an active issue quickly.

0 coins

I tried the callback feature twice too with similar results. The timing on the callback is completely unpredictable, which makes it hard if you have any other obligations during the day.

0 coins

they called me back at 7:08am which was not exactly convenient. at least they called i guess but the scheduling feature is misleading about what it actually does

0 coins

Good to know going in that it's unreliable. I'll try it as a backup but not count on it.

0 coins

Using it as a backup alongside other strategies makes sense. Just don't treat it as a solution by itself.

0 coins

Day eleven of my active issue here and something I want to flag for anyone who has a mix of W2 work and 1099 gig work in their history: the gig income reporting is handled completely differently in the Arizona DES system and it creates active issues at a much higher rate than regular W2 employment. I found this out the hard way. If you have any self-employment or gig income in the base period or during your current claim, specifically ask the adjudicator about how that income is being calculated. They apply a different formula and if you reported it in the standard wage section instead of the self-employment section, that's almost certainly your flag.

0 coins

I do have one 1099 client I do occasional work for and I've been reporting those earnings in the regular wages section. That might be exactly the issue.

0 coins

This is a really specific and useful point. The portal doesn't make the W2 vs 1099 distinction clear at all during weekly certification and I can see exactly how someone would put gig income in the wrong field.

0 coins

There's not even a warning or tooltip that explains the different sections are for different income types. It's genuinely a design failure in the portal that creates real problems for claimants.

0 coins

Even if you've been putting 1099 income in the right section, the way DES calculates partial benefit reduction for self-employment income is different from wages and can create apparent discrepancies that trigger flags even when you did everything right.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure