Back to Arizona Unemployment

Miguel Diaz

Unemployment claim showing 1 open issue after payment sent - Arizona DES help

Okay so this is stressing me out and I need to know if anyone else has dealt with this. I work in logistics and got laid off about six weeks ago when my company lost a major contract. Filed my claim right away, went through the whole process, and last week Arizona DES actually sent my first payment - I could see it posted on the CACTUS portal and everything looked good. But then today I logged back in to file my weekly claim and noticed there's now a flag on my account that says '1 open issue' and I have absolutely no idea what triggered it or what it means. The payment already went through. My bank shows the deposit. So why is there suddenly an open issue AFTER the money landed? I haven't changed anything about my situation - still unemployed, still doing my three job search activities per week, haven't turned down any work. Has anyone seen their unemployment claim showing 1 open issue after payment sent like this? Is my next payment going to be held up because of whatever this is? I tried calling Arizona DES but couldn't get anyone on the line.

Wait, is the issue flag sitting under your payment history tab or under the main claim summary? Because those are two completely different things and they mean very different stuff for what happens next. I went through something similar a few months back and spent three days panicking before I figured out how to actually get answers. Honestly the fastest thing that worked for me to reach a live Arizona DES agent was using Claimyr - you go to claimyr.com and they basically get you into the phone queue without you having to redial for hours. There's a video walkthrough at https://youtu.be/vwA1GGuV83Y that shows exactly how it works. I got through to someone within a couple hours and they were able to tell me exactly what the open issue was flagged for. In my case it was a wage crosscheck that triggered automatically when my former employer filed their quarterly report - nothing I did wrong, just a system thing that needed a human to clear it.

0 coins

The quarterly wage report thing - I had no idea that could trigger a flag even after payment goes out. My claim summary right now shows something similar and I've been blaming myself thinking I filled something out wrong.

0 coins

Mine is under the main claim summary page, not the payment history. So based on what you said that might be more serious? I'm going to look at that Claimyr option because I really need to actually talk to someone about this, not just stare at the portal.

0 coins

Quarterly crosschecks cause so many unnecessary flags its honestly ridiculous. The system should notify you WHY there's an issue not just that one exists.

0 coins

Had this exact scenario play out on my end earlier this year - went from approved payment straight into an open issue flag the next week. What nobody tells you upfront is that Arizona DES sometimes runs a secondary eligibility review even after releasing funds if something pops up in their backend verification. The payment going out doesn't mean your eligibility review is fully closed. So yes, your next weekly payment could be held pending resolution of whatever that issue is. The specific thing that tripped mine was that my former employer disputed part of my separation reason after the fact - they initially confirmed the layoff but then amended something in their response. I had to submit additional documentation through the CACTUS portal to clear it.

0 coins

Amended separation info AFTER already getting approved and paid - I didn't know employers could do that. That's a really unsettling thought. I had a pretty clean layoff with a letter and everything but now I'm second-guessing whether my company filed something weird.

0 coins

Employer-side amendments are more common than people think and they almost always create an adjudication flag. If you're stuck trying to reach someone to find out what specifically got flagged, Claimyr helped me get through to Arizona DES on a day when I'd already tried calling six times with no luck - claimyr.com - saved me from waiting another full week not knowing what was happening with my UI.

0 coins

Does submitting documentation through the portal actually work or does it just sit there unreviewed for weeks? Genuine question because I've uploaded stuff before and have no idea if anyone actually sees it.

0 coins

The portal uploads do get reviewed but the timeline is totally unpredictable. Sometimes cleared in days sometimes sitting there for three weeks.

0 coins

Okay so the open issue flag after payment - I learned this the hard way so let me save you some grief. Before I understood how Arizona DES post-payment reviews work I just ignored a flag thinking the payment meant everything was fine. Big mistake. What actually happens is the system can release a payment and simultaneously open a new issue if something triggers in a different part of the verification chain. They're not connected the way you'd expect. The payment processing and the eligibility review run somewhat independently. My situation involved a discrepancy between the wage data my employer reported and what I'd listed - even though both were accurate, the formatting difference caused the system to flag it. I ended up in a mini-adjudication even though I'd already received money.

0 coins

Mini-adjudication even after payment - that's exactly what I'm afraid is happening here. I want to make sure I keep filing my weekly claims while this gets sorted, right? I don't want to stop and have that cause a separate problem.

0 coins

Yes, absolutely keep filing. Stopping your weekly claim submissions while there's an open issue is one of the worst things you can do because then you've got gaps that are very hard to explain later. Keep doing your job search activities and logging them too.

0 coins

This happened to me last spring and I stopped filing for two weeks thinking the flag meant I shouldn't. Cost me those two weeks of benefits even after the issue resolved. Keep filing no matter what.

0 coins

Is this showing as an adjudication issue specifically or just a generic open issue? Because there's a difference in how those get handled and how long they typically take to resolve at Arizona DES. Generic open issues sometimes clear on their own within a week or two without any action needed from you. Adjudication issues require active resolution and can hold your payments for 3-6 weeks minimum. The portal language is frustratingly vague so if it just says 'open issue' without more detail you might need to call to find out the category.

0 coins

Just says '1 open issue' - no category, no explanation, no link to any further details. Zero context. How is that helpful to anyone?

0 coins

Mine said the same thing for two weeks and then just disappeared. Never found out what it was. Payment came through fine the whole time. So sometimes it really does resolve without explanation.

0 coins

Yeah the portal UI for issue flags is genuinely terrible. If the payment keeps coming it's probably a low-priority flag but if the next weekly claim gets held you'll need to escalate. That's when making phone contact with Arizona DES becomes really important.

0 coins

So frustrated reading this because the EXACT same thing happened to me and I still don't have a clear answer three weeks in. Filed my claim, got approved, received two payments, then this open issue appeared and now my third payment has been held. I've tried calling maybe fifteen times. The hold times are unreal and twice I got disconnected after waiting forty minutes. I genuinely don't know what I did wrong or what they need from me. The portal shows no pending tasks, no documents requested, nothing I can actually do. Just the flag sitting there.

0 coins

Three weeks with a held payment and no explanation - that's genuinely awful and shouldn't be allowed. Have you tried going in person to your local Arizona DES office? Sometimes a face-to-face visit gets faster results than the phone queue.

0 coins

Went in person last Tuesday. Was told they can't look at CACTUS portal flags in person and I need to call the claims line. So they sent me right back to the phone nightmare I can't get through.

0 coins

The in-person redirect to the phone line is infuriating - same loop I ended up in. The only way I finally got through was calling right when they open in the morning, literally dialing at 7:59am. Even then it took three tries.

0 coins

7:59am I'll try that tomorrow. I've been calling around 10-11 and apparently that's the worst possible time.

0 coins

Something people don't realize until it bites them - an open issue after payment can sometimes be triggered by your job search activity entries rather than anything about your employment history or separation. I had a flag show up because two of my job search contacts for one week were listed with the same employer name even though they were different positions. The system flagged it as a potential duplicate entry even though it was legitimate. Arizona DES requires that your three weekly job search activities be distinct and verifiable. I had to actually document with separate confirmation emails that these were two different job applications to the same company.

0 coins

Oh wow I didn't even think about the job search log as a possible source. I did apply to two positions at the same company last week - different departments, definitely different job postings, but same employer name on both entries.

0 coins

That could absolutely be it. I'd go back and add notes to each entry showing the specific job title and posting number so it's unambiguous. And consider having only one entry per employer going forward just to avoid the flag risk.

0 coins

Does Arizona DES actually audit the job search log that closely or is this more of a rare edge case? I've been kind of lazy about detail on mine and now I'm worried.

0 coins

They do spot-check and when they do they look at patterns. Same employer twice in a week is a pattern that can trigger review. Worth being thorough.

0 coins

Not trying to pile on with more doom but I want to be honest with you - I had an open issue flag that looked minor and ended up being a full adjudication that took almost eight weeks to clear. The difference between a quick resolution and a long one often comes down to whether you can get a human at Arizona DES to look at your specific file and confirm what category the issue falls into. Phone contact matters a lot here. After weeks of failed calls I ended up using Claimyr to finally get through - claimyr.com has the info and there's also a demo video at https://youtu.be/vwA1GGuV83Y - and what the agent told me in that call actually changed my whole approach to resolving the issue. Turns out there was documentation they needed that wasn't listed anywhere in my portal. Never would have known without talking to someone.

0 coins

Eight weeks is terrifying to even think about. I'm going to try getting through on the phone this week and if I can't get through I'll check out that Claimyr link. What kind of documentation ended up being missing from your file?

0 coins

In my case it was a separation agreement document that my employer had referenced in their response but hadn't attached. Arizona DES flagged my account waiting for the attachment but never sent me any notification. The agent was the one who finally told me what was actually missing.

0 coins

Missing attachments from employer responses that never get communicated to the claimant - this is such a common failure point in the system and it's completely preventable if they'd just send an automated notice.

0 coins

Does the open issue show any kind of reference number or code at all? Even something like a letter-number combination? Because sometimes those codes map to specific issue types and you can figure out what it is without having to call. When I was dealing with my own flag situation I found a sort of unofficial guide online that decoded some of the CACTUS portal status codes. Not perfect but helped me narrow down the category.

0 coins

Just checked and there's nothing - no code, no reference number, nothing clickable. Just the text saying there's one open issue. It's the least informative flag imaginable.

0 coins

That's unfortunately the most common version of the flag - the system acknowledges an issue exists without giving you any path to understand or resolve it. Phone contact really is the only way at that point.

0 coins

Why does the portal not at minimum link to a list of common issue types? Even that basic thing would help claimants so much. The design of this system seems intentionally unhelpful.

0 coins

Went through something adjacent to this - my claim showed clean, payment processed, then three days later an open issue appeared. What nobody mentioned in any of the official Arizona DES info was that there's often a 72-96 hour window after payment where the system does a final verification sweep. If anything catches during that sweep it creates a flag retroactively. The good news is that flags created during this post-payment sweep are often low severity and many clear automatically within the next billing cycle. The bad news is there's no guaranteed timeline and 'many clear automatically' is not 'all clear automatically.

0 coins

72-96 hour post-payment sweep - this is actually the most useful context I've gotten. So the timing of when my flag appeared (3 days after the deposit) might be meaningful and potentially a good sign?

0 coins

Potentially yes. Flags that appear in that specific window tend to be system-generated verification checks rather than employer-disputed or fraud-flagged issues, which are the more serious categories. Still worth monitoring closely and if your next payment gets held you need to act fast.

0 coins

The difference between a system-generated flag and an employer dispute flag in terms of resolution time is massive. One might clear on its own, the other requires active adjudication that can drag for weeks.

0 coins

Can I ask a potentially dumb question - when you file your next weekly claim with the open issue sitting there, does it let you submit it normally or does it block submission? Because I've heard conflicting things about whether an open issue locks your ability to file or just holds the payment.

0 coins

Usually still lets you file. The open issue typically holds the payment processing but doesn't block submission of the weekly claim itself. At least that's how it worked on my end - I could submit the claim, it just sat in pending longer than normal.

0 coins

Good to know I should still be able to file. I'll be watching that submission screen very carefully when I try this week.

0 coins

Confirm you can usually still file. But make a note of your confirmation number for every weekly claim submission while the issue is active - if anything gets disputed later having those confirmation numbers is really important.

0 coins

Real talk for a second - the open issue after payment thing tripped me up because I assumed 'payment sent' meant my claim was fully approved with no pending concerns. Learned the hard way that's not how Arizona DES works. Payment release and claim clearance are two separate system states and you can have one without the other. My cousin who works in insurance explained it's similar to how an insurance company can issue a payment and still have a file open for review - the payment is just one action in a process that might still have open threads.

0 coins

The two-separate-states explanation actually makes this make a lot more sense. I've been treating payment as the finish line when it sounds like it's more of a checkpoint.

0 coins

Payment as a checkpoint not a finish line - yeah that reframing actually helps. Annoying that Arizona DES doesn't communicate this anywhere but at least now I understand what I'm looking at.

0 coins

Honestly this forum explains the Arizona DES system better than the actual Arizona DES website does. No offense to whoever designed that portal but it assumes you already know things you have no way of knowing.

0 coins

Something that helped me when I had a flag I couldn't decode - I submitted a secure message through the CACTUS portal specifically asking for the issue category and reference number. I didn't hear back for about five days but when I did the response gave me enough information to understand what was actually being reviewed. It's not as fast as a phone call but it creates a written record and sometimes the response itself is enough to tell you whether you need to take additional action.

0 coins

Written record aspect is actually appealing - if this drags into an appeal situation having documentation of when I asked and what they said seems valuable. I'm going to send a message this afternoon.

0 coins

Yes, do it today and in your message specifically request the issue reference number and the anticipated resolution timeline. Those two specific asks tend to get more useful responses than a general inquiry.

0 coins

Does the secure message go to the same general pool as everything else or does it route to your specific adjudicator if one's been assigned? Because my messages have felt like they go into a black hole.

0 coins

Let me add something that got missed in this thread - are you currently on any kind of standby status with your former employer? Like did your company give any indication there might be a recall? Because if standby was indicated anywhere in your original claim and your employer is reporting you as permanently separated in their quarterly data, that discrepancy between standby status and permanent separation is a really common trigger for open issue flags even after payment has been released.

0 coins

No standby - my company lost the contract entirely, the whole division got eliminated. I was pretty explicit about that being permanent in my claim. But I'll double-check how I worded it in the original filing.

0 coins

Worth verifying. Even language like 'possible future positions' in a separation letter can get flagged as a standby indicator if the system parses it a certain way. If your letter says anything about rehire eligibility that could be enough.

0 coins

My letter says I'm eligible for rehire if the company opens similar roles in the future, which is pretty boilerplate corporate language. Could that actually be causing an issue?

0 coins

Possibly yes. That rehire eligibility language sometimes reads to the Arizona DES system as an indication of non-permanent separation. It's worth clarifying in a written response that this is standard language and your layoff was definitive with no recall arrangements.

0 coins

Just want to validate that this situation is incredibly stressful and confusing and you're not overreacting by being worried. The vagueness of these flags is a real problem. I've been through the Arizona DES process twice now and both times the portal gave me almost zero actionable information when things got complicated. The only times I actually understood what was happening with my claim was when I managed to speak with an actual human agent. Everything else - portal messages, automated callbacks, the FAQ pages - gave me information that was either too generic or just wrong for my specific situation.

0 coins

Thank you for saying this - I genuinely have been second-guessing whether I'm overreacting. The portal is so opaque and when you have bills due it's hard to stay calm about a flag with no explanation.

0 coins

Not overreacting at all. Document everything, keep filing, and push hard to get phone contact with Arizona DES. The claimants who resolve these issues fastest are always the ones who managed to reach someone by phone.

0 coins

Okay update from my own experience that might be directly relevant - I had an open issue flag appear about 48 hours after a payment posted and I was getting nowhere trying to reach Arizona DES through normal channels. Someone on another forum thread recommended Claimyr and I was skeptical but tried it - claimyr.com - and within a few hours I was talking to an actual Arizona DES rep. What she told me was that my flag was a routine income crosscheck against my previous year's wage records that had been delayed and ran late. Zero action required from me, it was scheduled to clear in their next processing cycle. I had been catastrophizing for days over something that was already resolving. Knowing that made a huge difference.

0 coins

Routine crosscheck that was already resolving - okay that is genuinely the best possible outcome to hear about. Going to try calling directly first this week but if I keep hitting walls that Claimyr option is my next step.

0 coins

Yeah definitely try calling first, nothing wrong with that. I just had run out of patience with the hold times and disconnections by the time I tried it. The main thing is getting actual human clarification because the portal alone will drive you crazy.

0 coins

Routine crosschecks that run late and trigger flags without any notification to the claimant are such a design failure. If the system knows a crosscheck is pending it should tell you so.

0 coins

Something practical to do right now while you're waiting to reach someone - go back through your claim and your weekly certifications and screenshot everything. Every page that shows your claim status, your payment history, your job search log, the open issue flag itself. If this escalates to any kind of formal adjudication or appeal having dated screenshots of every system state is incredibly useful because the portal doesn't always preserve historical data the way you'd expect.

0 coins

Already started doing this after reading the thread. Have screenshots of the flag, the payment confirmation, my job search entries. Will add screenshots of my weekly claim submissions going forward.

0 coins

Good. Also keep a simple log in a notes app of every time you call Arizona DES - date, time, how long you waited, whether you reached anyone, what they said if you did. That paper trail matters.

0 coins

The screenshot advice is so important and nobody tells you this upfront. Lost track of some key portal states during my adjudication because I assumed the history would be there and it wasn't.

0 coins

Random thing I noticed when my own account had a flag - the open issue sometimes shows up as a downstream effect of your former employer filing their UI response late. Arizona DES has a window where employers respond to separation claims and if they respond right around or slightly after your first payment processes, the system can generate an issue flag when it registers the late employer response even if the content of their response doesn't actually dispute anything. The flag is basically the system going 'wait, new employer input arrived, need to reconcile' rather than 'employer is disputing your claim.

0 coins

Late employer response that doesn't dispute anything but still triggers a flag - is there any way to find out if that's what happened without calling? Like does the portal show employer response status anywhere?

0 coins

Not obviously, no. There's no clear employer response tracker in the claimant portal. Sometimes if you dig into the claim detail pages there are timestamps that imply when employer contact occurred but it's not labeled clearly.

0 coins

This is actually a really common cause of post-payment flags and you're right that it's often benign. The timeline of when the employer submitted their response relative to when the payment processed tells you a lot about what triggered the flag.

0 coins

Can I offer a slightly different perspective? Everyone here is kind of assuming the flag is a problem to solve but sometimes doing nothing while monitoring your next payment is the right move. If your payment came through and the flag appeared with no document requests and no held payments yet, the flag might just be an informational marker in the system that clears on its own. Not every open issue flag requires active intervention. The question is whether your NEXT weekly payment processes normally. If it does, the flag probably resolved on its own. If it gets held, then you need to escalate hard and fast.

0 coins

Monitor the next payment as the real diagnostic - that's a useful frame. I think I'm going to try reaching someone by phone this week just to understand what the flag actually is, but you're right that the next payment will tell me whether it's already resolving.

0 coins

This is probably the most practically useful advice in the thread honestly. The flag is information but held payment is the actual problem to respond to.

0 coins

Exactly. Flags without held payments are annoying but not emergencies. Held payment is when you shift into active resolution mode and start escalating.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure