Back to Arizona Unemployment

Kevin Bell

Arizona DES new CACTUS system username security question not set - anyone else dealing with this?

So I finally sat down to log into the new CACTUS portal to file my weekly claim and ran into a wall I did not see coming. When I try to get past the login screen it keeps throwing an error saying my security question hasn't been configured. I never got any notification that I needed to set one up when they migrated everyone over to the new system. My old login credentials from the previous portal worked fine until about two weeks ago and now suddenly I'm locked out because of this security question thing. My situation is that I've been on standby status with my employer and have been filing weekly claims consistently for about three months. Missing even one week could mess up my entire claim and I genuinely cannot afford that right now. The CACTUS portal is supposed to make things easier but right now it's doing the opposite. I've tried the standard account recovery link on the login page but it loops me back to the same error. Tried a different browser too, same result. Called the main Arizona DES line and sat on hold for two hours before getting disconnected. Does anyone know if there's a specific fix for this or a direct number to reach the tech support team at DES?

The transition to the new CACTUS setup really did catch a lot of people off guard with the security question requirement. I went through almost the exact same thing about six weeks back - couldn't get past that screen no matter what I tried. What finally worked for me was going to the login page and clicking the 'forgot username' path instead of the account recovery option, which sounds weird but it actually triggers a different reset flow that prompts you to set your security question from scratch. Worth trying before you spend more time on hold.

0 coins

Is the 'forgot username' link in the same place as the regular account recovery or is it somewhere different on the page? I want to make sure I'm clicking the right thing because every time I've tried something new it just loops me around.

0 coins

That forgot username path definitely worked differently when I tried it, though my issue was slightly different from the security question error. The reset flows in the new CACTUS system seem to handle different account states differently so results vary.

0 coins

Two hours on hold and then getting disconnected is honestly one of the most infuriating things about dealing with Arizona DES - been there multiple times and it never gets less frustrating. Someone in another thread pointed me toward a service called Claimyr after I described basically the same phone situation. You go to claimyr.com, they hold the line for you and call you back when an actual Arizona DES agent picks up. There's a video walkthrough at https://youtu.be/vwA1GGuV83Y if you want to see how it works before trying it. With a standby claim and weekly filings at stake I wouldn't keep gambling on the phone queue.

0 coins

Wait, so they actually stay on hold on your behalf and then connect you once someone answers? I wasn't sure how something like that could even work but if it means not losing two hours just to get disconnected I'd look into it.

0 coins

Claimyr worked for me when I was trying to get my adjudication issue looked at. I was skeptical at first but the callback actually came through and the agent I spoke to was able to pull up my account right away.

0 coins

gonna look at that video, two hours on hold is insane for what sounds like a basic account fix

0 coins

The security question thing in the new CACTUS portal is a real pain point that DES hasn't communicated well. What surprised me was finding out you only have a 10-day window after your account migration to set it up before it locks you out of certain functions - I didn't see that anywhere in the emails they sent. If you're past that window the self-service reset options on the portal don't have full access to fix it, which is why the loops keep happening. You essentially need a live agent to flag your account for a manual security reset on the backend.

0 coins

Ten days and nobody mentioned that anywhere? Did you find that out from an agent or is it written somewhere I missed?

0 coins

That tracks with what happened to my cousin - she tried to fix it herself for two weeks and nothing worked until an agent manually reset something on their end. The portal really should give a clearer error message explaining that instead of just looping.

0 coins

The lack of communication about that window is wild. I work in HR and I've had three employees come to me confused about this exact issue after the CACTUS migration.

0 coins

ok so basically the only real fix is calling them, got it. wish the website just said that instead of sending people in circles

0 coins

Honestly your standby situation makes this more urgent than a regular claim would be. Missing a weekly filing when you're on standby status can trigger a whole review of whether you're still meeting the availability requirements. I had a gap in my weekly claims once - only about nine days - and it kicked my claim into adjudication because DES flagged it as a potential break in eligibility. Took almost three weeks to sort out even though my employer confirmed the standby was still active.

0 coins

Nine days was enough to send it into adjudication? That's what I'm afraid of - I'm already at almost two weeks of not being able to log in and file.

0 coins

The adjudication trigger from missed standby filings is real. The system doesn't automatically know you had a technical issue, it just sees the gap and flags it. Document everything - screenshots of error messages, times you tried to call, all of it - in case you need to explain the gap later.

0 coins

This is exactly why I always screenshot confirmation pages every single week. The CACTUS system is new enough that bugs like this are going to happen and you want a paper trail.

0 coins

Something I didn't see mentioned yet - have you tried accessing CACTUS from a completely different device? Not just a different browser but a phone or a tablet you haven't used before. The new system has some cookie or session caching issue that can persist across browsers on the same machine. When I had an account error a few months back nothing worked on my laptop but logging in fresh on my phone got me further in the process even if it didn't fully solve things.

0 coins

Haven't tried a completely different device yet, only switched browsers on the same computer. Worth a shot before I go further down the phone rabbit hole.

0 coins

The device thing is actually a decent tip. Fresh session on mobile cleared a weird redirect loop I was stuck in. Didn't fix my underlying account issue but got me to a different error screen that was actually more informative.

0 coins

tried this when my account was doing something similar and it helped me at least see a different error code which gave me something specific to tell the agent when I called

0 coins

I want to flag something for anyone reading this thread who thinks the forgot-password or forgot-username flows will solve a security question error - in my experience with the new CACTUS system those paths reset your login credentials but they don't touch the security question layer. The security question is a separate authentication tier that was added during the CACTUS migration and it has its own reset process that only agents can initiate. I went through four different self-service resets thinking I was fixing it and each time the same error came back the moment I tried to do anything beyond basic login.

0 coins

Four resets and it still came back every time - that really confirms I need to get an actual person on the phone rather than keep trying portal workarounds.

0 coins

Went through something similar and after wasting a week on the self-service options I finally got through to Arizona DES using Claimyr. The agent confirmed exactly what you said - the security question reset has to be done from their side, there's no claimant-facing fix for it once it locks. The site is claimyr.com and there's a demo video at https://youtu.be/vwA1GGuV83Y if anyone wants to see the callback process before signing up.

0 coins

This is the clearest explanation of why the loops happen that I've seen in this thread. The two-layer auth system is new and DES really didn't document it properly anywhere public facing.

0 coins

Just want to add from personal experience that when you do reach an agent about this, specifically use the phrase 'CACTUS security question not configured' because that's what gets them to the right department notes. I said something vague the first time I called and the agent tried walking me through the standard password reset process which I'd already done three times. Second call I used that exact phrasing and was transferred to someone who knew exactly what I was describing and had the fix done in about fifteen minutes.

0 coins

Specific phrasing like that actually makes a difference in getting routed to the right person? I would not have thought to say it that way, I would've just described it generally.

0 coins

Exact wording matters a lot with Arizona DES calls - agents are trained to match keywords to issue categories. I found Claimyr helpful for making sure I actually got to an agent to use those words since the hold times made it hard to even get to that point. Claimyr.com is where I signed up. For a security question issue that's blocking weekly filing access, getting that call through sooner is better.

0 coins

This is genuinely useful advice. I've noticed the same thing - vague descriptions get you standard troubleshooting scripts, specific technical language gets you to someone who knows what they're doing.

0 coins

Coming back to the standby piece because I think it's being slightly underweighted in this thread - when you do reach Arizona DES about the CACTUS account fix, ask the agent to also note in your claim file that your inability to file weekly claims was due to a verified system error. Some agents will add an internal note that can protect you if the missed weeks trigger an adjudication review later. Not all of them volunteer to do this but most will if you ask directly.

0 coins

Asking them to add a note to the file proactively is something I definitely wouldn't have thought to request on my own - is that a formal process or just something agents can do at their discretion?

0 coins

It's at agent discretion but it's a recognized thing they can do. When my claim had a gap caused by a DES portal error an agent added a system note that essentially flagged the gap as non-voluntary and my adjudication review was resolved pretty quickly once a reviewer saw that note.

0 coins

Seconding this advice strongly. The note in the file is what saved me when my standby claim got flagged. Without it I would've had to go through a full appeal process.

0 coins

did not know agents could add protective notes like that. genuinely helpful thread

0 coins

There's a lot of focus on the phone solution here and it's definitely the right one, but I want to mention that Arizona DES also has an online contact form through the CACTUS portal - except the irony is you can't access it if you're locked out by the security question error. I checked because I was hoping there was a way around the phone queue and there isn't for this specific issue. The email and message options are all gated behind the same login wall.

0 coins

So every digital path to contact them requires the account access that's broken - that's a pretty significant design flaw they should've thought through.

0 coins

It's a catch-22 that affects more account issues than just this one. The only fully external contact method is the phone line, which is why the hold times are what they are. Every locked-out user has no option but to call.

0 coins

this is honestly terrible system design, like why would you gate support contact behind the broken thing

0 coins

Quick update on the device tip from earlier - I just went through this exact issue last month and what actually worked for getting past the initial error enough to reach a different screen was clearing site data specifically for the CACTUS domain rather than just clearing all browser history. In Chrome you can go to Settings, then Privacy, then Site Settings, search for the CACTUS URL and clear just that site's stored data. Gave me a genuinely fresh session rather than a cached one.

0 coins

Clearing data for just that specific domain rather than everything - is there a risk that clears anything I actually need like claim confirmation records?

0 coins

Clearing site data for just the CACTUS domain only removes cached session and login data, not anything stored on DES servers. Your claim records, filing history and payment information all live on the DES backend, not in your browser.

0 coins

Good tip on the targeted clear. I always did full browser clears which probably explains why I'd have to re-enter settings for other sites every time I tried to fix a DES login issue.

0 coins

Something that isn't talked about enough in these CACTUS threads - the new system actually has two separate help lines, the main DES number most people know and a dedicated CACTUS technical support line. The technical support line is shorter because fewer people know about it and they're specifically trained on portal account issues rather than claim eligibility questions. I don't have the number handy but if you search Arizona DES CACTUS technical support on the main des.az.gov page it should come up in the contact section.

0 coins

A separate technical line with shorter waits sounds exactly like what I need - is it available the same hours as the main line or does it have different hours?

0 coins

The technical support line I'm aware of runs Monday through Friday during standard business hours, slightly narrower than the main claims line. Worth checking the DES website directly since hours have shifted a few times since the CACTUS rollout.

0 coins

The existence of a separate tech line is not communicated anywhere obvious on the portal itself. Most people just call the main number and wonder why the agents don't seem trained on portal-specific issues.

0 coins

ok this might be a dumb question but can you just file your weekly claim by phone instead of through CACTUS while your account is locked? i thought there was still a phone filing option somewhere

0 coins

There is a phone filing option and it's worth asking about when you call. The IVR system for weekly claims is separate from the CACTUS portal so a lockout on the portal doesn't necessarily block the phone filing path. Arizona DES has had phone claim filing as a backup option for claimants who can't access the online system.

0 coins

Phone filing being separate from the portal is actually really useful to know - if that's real it could solve the immediate problem of missing weekly claims while the account fix is pending.

0 coins

Confirm the phone filing is real. The IVR weekly claim line is 1-877-600-2722 for anyone who needs it. It's a bit clunky but it works and processes the same as the online filing.

0 coins

This is probably the most immediately practical thing in the whole thread. File by phone to protect the claim while sorting out the CACTUS account issue separately.

0 coins

The fact that you can file by phone while sorting out the CACTUS issue is a relief but I'd still push to get the account fixed fast because the phone IVR has its own quirks - for standby status specifically there are a couple questions in the phone filing flow that word things differently than the portal does and people sometimes answer them wrong which can create its own eligibility issues.

0 coins

Different wording on standby questions in the phone filing flow - what kind of questions trip people up? I want to make sure I answer correctly if I go that route.

0 coins

The main one I've seen cause problems is the 'able and available for work' question on the phone system. For standby claimants it still needs to be answered yes even though you're technically waiting for your employer to call you back. Some people answer no because they think standby means they're not available for other work, which can flag the claim.

0 coins

The able and available question is the classic standby trap. Standby status means your employer is your expected return-to-work, but DES still considers you available for work generally. Yes is always the right answer for that question on standby.

0 coins

been following this thread because i had a similar thing happen last week. my security question was apparently set but kept saying it wasnt. turned out the question itself had special characters in it that the new system doesnt accept and that was causing the validation to fail even though an answer existed. agent told me this is apparently a known bug they're working on

0 coins

Special characters in the security question causing silent failures is a really specific bug - did the agent say whether that affects all special characters or only certain ones?

0 coins

That would explain a lot of cases where people swear they set the security question but still get the error. The validation bug with special characters seems like something that should've been caught before launch.

0 coins

Known bugs that agents are aware of but that aren't communicated publicly are frustrating. How is a claimant supposed to know their security question has an invisible formatting issue?

0 coins

Pulling together the practical path here because this thread has gotten long - phone file your weekly claim using the IVR at the number someone shared above so you don't miss your filing while this is unresolved. Then call the CACTUS technical support line, use the specific phrase 'CACTUS security question not configured,' and ask the agent to do a manual security question reset from the backend. Also ask them to add a note to your claim file about the portal access issue in case the missed weeks get reviewed. That's the full sequence.

0 coins

This actually lays out everything I need to do in order - appreciate someone putting it together clearly. Going to try the phone filing first and then tackle the account call.

0 coins

Good summary. One more thing to add for the phone call - if the hold times are killing you, Claimyr at claimyr.com can hold the line and call you back when an agent answers. With the technical fix needing a live agent anyway it's worth not wasting more two-hour hold attempts that might disconnect. Demo at https://youtu.be/vwA1GGuV83Y if you want to see how it works.

0 coins

The sequence makes sense. I'd also suggest timing the call for right when the lines open in the morning since technical support tends to have shorter waits at opening than mid-morning when volume peaks.

0 coins

One thing I want to flag that might matter for OP's situation - when you're on standby and you do get back into your CACTUS account, double check that your standby status is still accurately reflected on the portal. During the migration some accounts had their claim details not fully transfer correctly and standby designations in particular were sometimes dropped or changed to a standard 'laid off' status which has different job search requirements. Worth verifying before you file your next online claim after the fix.

0 coins

Standby status being dropped during migration is not something I would've thought to verify - what section of the CACTUS portal shows whether the standby designation is correctly applied?

0 coins

In the new CACTUS portal look at your claim summary page, there should be a claim type or claim status field that specifies standby. If it shows something different or is blank, that's worth flagging to an agent in the same call where you get the security question reset.

0 coins

Migration errors on standby status are real and genuinely change your weekly filing obligations. Regular layoff status requires active job search documentation every week - standby status has different requirements - so if that got changed without your knowledge you could inadvertently be out of compliance.

0 coins

For whoever reads this thread later having the same problem - the whole chain of issues here is basically a documentation and communication failure by Arizona DES during the CACTUS rollout. The security question requirement, the migration window, the special character bug, the separate technical support line - none of this was clearly communicated to claimants. It's worth knowing that if you end up in adjudication because of missed filings caused by the portal error, that's an adjudication you should be able to win if you document your attempts to access the system and to reach DES.

0 coins

Documentation of access attempts being useful in adjudication makes me feel better about keeping screenshots of all these error messages - I've been doing that since day one of this problem.

0 coins

Screenshots with timestamps are your best friend for any adjudication that stems from a technical issue. DES reviewers generally respond well to concrete documentation that shows you tried to comply and the system prevented you.

0 coins

This thread should honestly be pinned somewhere. The amount of practical information here - phone filing backup, the technical line, the specific phrasing, the note request - is way more than what DES actually tells you when this happens.

0 coins

Agreed. The only thing I'd add is that adjudication appeals specifically for missed filings due to system errors have a 15-day response window from when DES notifies you, so don't sit on it if that notice comes in.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure