Back to Arizona Unemployment

Carmella Fromis

Unemployment won't let certify next week already certified - Arizona DES issue

Okay so I'm completely confused right now and kind of freaking out. I went into the CACTUS portal this morning to do my weekly certification and the system is telling me I can't certify because I already certified for that week. The thing is I definitely did NOT certify for next week yet - I certified for the current week that just ended, which makes total sense. But the portal seems to think I already did next week too? I work in landscaping and got laid off about 6 weeks ago when my employer lost a major contract. I've been doing everything right - logging my job searches, filing on time, the whole deal. This week I went in like normal and after I finished certifying, I noticed the portal was showing a future week as already complete. I didn't do that. I didn't even click on anything weird. Now I'm worried that if the system thinks I already certified for a week I haven't lived through yet, it'll either block me from certifying when that week actually comes up, or worse, flag my account for trying to double-certify and mess up my whole claim. Has anyone seen this glitch before? Do I need to call Arizona DES to fix it or will it sort itself out? I really can't afford to miss a payment right now.

Wait, is it showing the week as 'certified' or as 'pending' or something else? The CACTUS portal labels things in really confusing ways and sometimes a week showing as already processed just means Arizona DES is pre-loading your next certification window, not that you actually submitted it.

0 coins

Good point - it says 'certified' in what looks like a green status. Not pending, not in progress. Full on certified with a checkmark basically. That's what's freaking me out.

0 coins

Yeah the green status is the weird one. I've seen it flip to that prematurely before on my account and then it went back to normal before the week opened up. Might just be a display bug.

0 coins

Ugh this exact thing happened to me two months ago and I spent three days trying to get through to Arizona DES on the phone with zero luck. Someone in another thread told me to try Claimyr - it's basically a service that gets you connected to an actual Arizona DES agent without you having to sit on hold forever. I was skeptical but I used it and got through within an hour. You can check it out at claimyr.com and there's a demo video at https://youtu.be/vwA1GGuV83Y that shows how it works. For a glitch like this you really do need a live agent to look at your account and manually clear it - the portal won't fix itself if it's actually recorded a false certification.

0 coins

Okay thanks - did the agent actually fix it on the spot when you called, or did they just open a ticket and make you wait?

0 coins

Seconding this - portal glitches that show wrong certification status almost never self-correct. You need someone to touch the account from the backend.

0 coins

Does that service work for Arizona specifically? I've heard it mentioned for other states but wasn't sure about Arizona DES.

0 coins

Yeah it's what I used for my Arizona DES claim. Got connected to the actual DES line, not some random call center.

0 coins

So here's the thing that caught me off guard when I first dealt with Arizona DES certifications - the system locks your ability to certify for a given week the moment it registers a submission, even a partial or accidental one. What that means in plain language is if the portal recorded any kind of input under your account for that future week, it treats it as done. You can't go back in and redo it yourself. An agent has to reset it from their end.

0 coins

Wait, so even if I never saw a confirmation screen, it could have still recorded something?

0 coins

Exactly. Sometimes the system logs the week as certified if you clicked into the certification flow and your session timed out or the page errored. It's a known issue that DES agents can fix but it does require a phone call.

0 coins

This happened to my brother in law last year. He never finished filling out the form, thought nothing went through, but the system had it marked done. Took about a week to fix after he got through to someone.

0 coins

Have you tried logging out completely and logging back in? Sometimes the portal shows stale data and a fresh login refreshes it. Not saying that'll fix an actual glitch but worth ruling out before you spend an hour on the phone.

0 coins

Tried that already, same thing both times. Even tried a different browser.

0 coins

Dang okay yeah that rules out the display refresh theory. Definitely an account-level issue then.

0 coins

Different browser is a good test. If it shows the same in Chrome and Firefox then it's not a local cache thing, it's server-side.

0 coins

Three weeks before my claim finally got straightened out I was in almost this exact situation. What nobody tells you is that Arizona DES has a specific window - I think it's something like 30 days after the affected week closes - where they can administratively correct a certification error. If you wait too long the week just falls off and you lose that payment permanently. So don't sit on this.

0 coins

Okay that's genuinely scary - so there's a deadline for getting this corrected?

0 coins

From what the agent told me, yes. They can backdate corrections but only within a certain period. The sooner you call the better your odds of getting the week fixed and paid out.

0 coins

Can confirm there's a correction window. I've also heard it described as being tied to when the week's payment would have originally processed, not a fixed number of days, but either way acting fast matters.

0 coins

Okay real talk - is anyone else perpetually confused by the CACTUS portal? Like I genuinely cannot tell half the time whether my certification went through or not. The confirmation screen disappears so fast.

0 coins

Oh my god yes. I screenshot everything now because I don't trust it.

0 coins

Screenshotting is actually genius, I'm starting that immediately.

0 coins

The confirmation email is supposed to arrive within a few minutes of certifying. If you don't get one, that's a sign something might not have saved correctly.

0 coins

Just want to flag something - I've seen a few people on here say the portal glitch fixes itself and to just wait. In my experience that's really risky advice for something involving your weekly payment. Arizona DES doesn't automatically audit for display errors and issue corrective payments. If the system thinks you already certified a week, it will skip that week's payment without any notification to you.

0 coins

This is a fair point. The 'just wait and see' approach works for things like a pending adjudication status but NOT for a certification that the system thinks is already complete.

0 coins

Exactly - adjudication pending means they're reviewing your claim. A certification already marked complete means to the system there's nothing left to do for that week. Very different situations.

0 coins

This thread is making me more stressed but also more motivated to get this fixed today. I really appreciate everyone clarifying this.

0 coins

Okay so I work adjacent to HR and have dealt with DES on behalf of employees before - the fastest path I've seen work is calling the main DES line first thing when it opens (like right at 8am) and specifically asking the agent to pull up your certification history and confirm whether a manual entry exists for the future week. If they see the entry they can delete it and reset the week status.

0 coins

Eight AM sharp, got it - is that Arizona time or does it vary?

0 coins

Arizona doesn't do daylight saving so it stays on MST - 8am local Arizona time is what you want. The queue is significantly shorter in that first half hour than it is by 9 or 10.

0 coins

The early morning tip is real. I've tried calling at 10am and sat on hold for two hours. Called at 8:05am another time and got through in 20 minutes.

0 coins

For anyone who can't do the 8am thing because of work or kids or whatever - I found Claimyr really useful for this kind of situation where you need to reach Arizona DES but can't babysit a phone all morning. The site is claimyr.com and there's a walkthrough video at https://youtu.be/vwA1GGuV83Y - it essentially handles the hold queue part for you and calls you back when an agent is available.

0 coins

Oh interesting - so you don't have to actually sit on hold yourself?

0 coins

Right, you're not holding, you're just waiting for a callback. Made it way easier for me since I was job searching during the day and couldn't be tethered to a phone.

0 coins

That's actually huge for people who are actively working part time while on UI since you can't always be available during business hours.

0 coins

Something worth knowing - if you do get through to an agent and they tell you there's no error on their end, ask them to read back exactly what date range the certified week shows. Sometimes the portal and the agent's system are out of sync and what looks wrong on your end is actually correct on theirs.

0 coins

Good call - what do I do if they say everything looks fine but my portal still shows the wrong status?

0 coins

Ask them to send you a written confirmation of your certification history to your DES account message center. That way you have documentation if you get a payment discrepancy later and need to dispute it.

0 coins

The message center documentation tip is gold, I wish I'd known that during my claim issues.

0 coins

Honestly I'm kind of surprised more people haven't run into this. I feel like the CACTUS portal has been extra buggy the last couple of months. I've had weird status displays three times in the past 8 weeks.

0 coins

It's been rough. I think they pushed some kind of update and it introduced issues. My weekly claim summary page completely disappeared for two days last month.

0 coins

Exactly! And there's no status page or announcement from DES when these things happen, you just have to figure it out yourself.

0 coins

The lack of communication from DES during system issues is SO frustrating. Even just a banner on the login page saying 'we know, we're working on it' would help.

0 coins

Something I want to add for anyone reading this later - if you're dealing with a certification glitch, write down the exact date and time you first noticed the issue before you call. Agents can sometimes look at server logs and having a specific timestamp helps them narrow down what happened.

0 coins

Really good tip, I just did exactly that and took a screenshot of the status screen with the timestamp visible.

0 coins

Perfect. Also note which browser and device you were using when you noticed it, they sometimes ask that for tech issue reports.

0 coins

Late to this thread but wanted to add - I had a certification issue that I thought was a glitch but turned out Arizona DES had opened an adjudication on my account without notifying me, and the system was blocking my next certification as a result. The two things looked the same on the portal. When I finally got through to an agent (used Claimyr at claimyr.com to get past the hold queue, would recommend) they found the adjudication flag immediately. Might be worth asking about that specifically when you call.

0 coins

Whoa I hadn't even considered that possibility. What would trigger an adjudication that I wouldn't know about?

0 coins

Could be something a previous employer reported, a discrepancy between your work search log and employer records, really a bunch of things. DES doesn't always send a notice right away.

0 coins

This is an important point. A hidden adjudication can manifest as a lot of different portal errors that look like technical glitches but are actually account holds. Good reason to have an agent look at the full account picture, not just the certification status.

0 coins

OP, did you have any employer separation issues when you first filed? Like did your former employer contest the claim or did you have to go through any initial adjudication? Sometimes those leave flags on the account that cause downstream issues with certifications.

0 coins

No contest that I know of - my employer was pretty straightforward about it being a layoff due to losing a contract. I did have a one-week waiting period at the start but that was it.

0 coins

Okay, that's a good sign. The waiting period is standard and doesn't indicate any flag. The lack of employer contest makes the hidden adjudication scenario less likely but not impossible.

0 coins

Employer contests can still come in late, weeks after the initial approval. I'd still ask the agent to confirm there's no active adjudication or pending issue on the account while you have them on the line.

0 coins

Has anyone noticed if this kind of error affects the job search requirement reporting too? Like if the system thinks you already certified, does it also think you already submitted your job search activities for that week?

0 coins

Great question - job search activities are logged as part of the certification in CACTUS, so yes, a false certification would likely also mark those as submitted. Which creates a problem if the week eventually gets reset because you'd need to resubmit them.

0 coins

That's a mess. So fixing the certification glitch could potentially wipe out your logged job search activities for that week?

0 coins

In theory yes. When an agent resets a certification the whole week's data can get cleared. Best practice is to have your job search activities documented somewhere outside the portal before calling so you can re-enter them quickly.

0 coins

For what it's worth I reported a similar portal issue to DES through the online contact form once and never heard back. The phone call is really the only thing that works for account-specific issues like this.

0 coins

The contact form feels like it goes into a black hole honestly.

0 coins

I waited three weeks for a response and by the time anyone replied the issue had either fixed itself or been fixed by a phone call I eventually made. Total waste of time.

0 coins

They need a live chat option so badly. So many of these issues could be resolved in five minutes if there was a text-based support option.

0 coins

Quick update request OP - have you been able to reach anyone yet? Curious whether this turned out to be a display glitch or an actual account issue.

0 coins

UPDATE: Got through this morning around 8:15am after trying for about 40 minutes. The agent found that there was actually a partial session from two days ago where I'd apparently started the wrong week's certification by mistake, hit back, but the system had already logged it as initiated. She was able to clear it and reset the week status. No adjudication, no flags, just a glitch. She confirmed my correct certified week is paid and the future week is now back to 'not yet available.' So relieved.

0 coins

That's such a good outcome! And it confirms what people were saying - the portal logs things even when you think you backed out of them.

0 coins

Really glad you got it resolved fast. Saving this thread to share with people who have similar issues because the advice in here is solid.

0 coins

The partial session thing is such a known bug and DES really should have a warning about it. Glad you got it sorted before it affected your payment.

0 coins

For anyone who finds this thread later: the takeaway is that if the portal shows an unexpected certification status, don't assume it'll self-correct and don't wait more than a day or two. Call Arizona DES directly and ask an agent to review your certification history. The window to fix these things isn't infinite and a missed week means a missed payment that may be hard to recover.

0 coins

Perfect summary. I'd add: document everything before you call. Screenshot the wrong status, note the timestamp, have your claim ID ready. Makes the call faster.

0 coins

Also screenshot your confirmation emails every week as ongoing proof you certified correctly. Future you will thank you.

0 coins

And if you can't get through on the phone, the Claimyr option mentioned earlier in this thread is worth looking at - getting stuck in an infinite hold loop when there's a time-sensitive account issue is a real problem.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure