Can you fix duplicate job contact on DES weekly certification?
So here's my situation - I work in logistics and got laid off about six weeks ago. Filed everything properly, been doing my weekly certifications without any issues until this past Sunday. When I was filling out my job search activities for the week, I accidentally entered the same employer contact twice. Same company name, same date, everything. Hit submit before I noticed the mistake. Now my weekly certification is showing as submitted but I'm worried this duplicate entry is going to flag my claim for some kind of review or mess up my job search log. I tried going back into the CACTUS portal to edit it and there's no option to remove or modify an already-submitted certification. Called DES and sat on hold for two hours before the line just disconnected. Does anyone know if a duplicate job contact entry on a weekly certification is actually a problem? Can Arizona DES fix it on their end if you report it? Or does this just sit there and cause issues down the line? Really stressed about this because my payments have been fine and I don't want anything to derail that now.
67 comments

Evan Kalinowski
Weekly certifications once submitted are locked - that's just how the CACTUS system works, there's no self-service edit option after you hit submit. What I'd do first in your shoes is document everything right now, screenshot your submitted certification showing both entries, and write down the exact dates and employer name. That paper trail matters a lot if this ever comes up during adjudication. The rule itself is pretty straightforward: DES requires three job search contacts per week, and duplicate entries don't count as separate contacts. So technically you only have two valid contacts logged for that week, not three. That's the actual risk here, not fraud or disqualification - it's the possibility of being found short on your required job search activities for that week.
0 coins
The Boss
AuthorAlready took screenshots right after I realized what happened. So the concern is really about only having two valid contacts rather than the duplicate itself being flagged as dishonest reporting?
0 coins
Victoria Charity
Yep that's the real issue. DES doesn't automatically audit every entry for duplicates but if your claim ever gets reviewed they'd catch it and potentially deny that week's payment for insufficient job search contacts. Better to get it corrected proactively.
0 coins
Jasmine Quinn
This happened to my cousin too, same exact thing, submitted and realized the duplicate after. DES ended up not caring about it at all when they reviewed his claim months later. Though that could have just been luck tbh.
0 coins
Oscar Murphy
First thing I'd actually do is call DES and report the error yourself before they find it. Proactive disclosure goes a long way with these things. You'd be surprised how often agents can add a note to your file that essentially flags the error as a known honest mistake rather than something that looks like you were padding your job search log. The job search requirement for Arizona DES is three contacts weekly, so having a duplicate technically leaves you one short unless you have additional contacts you forgot to add.
0 coins
The Boss
AuthorThat's what I figured, calling to get ahead of it. The problem is I've tried calling and can't get through. Two hours on hold and then disconnected. Is there a better way to reach them?
0 coins
Nora Bennett
Getting through to DES by phone is basically a part-time job in itself. Early mornings right when they open at 8am give you slightly better odds but it's still rough.
0 coins
Ryan Andre
Try the online message center in your CACTUS account too. Send a written message describing the duplicate entry with your certification week dates. That creates a timestamped record even if no agent responds quickly.
0 coins
Lauren Zeb
Since you're hitting the phone wall, worth knowing about Claimyr - claimyr.com. It's a service that handles the hold queue for you and calls you back when an actual DES agent picks up. For something like this where you specifically need an agent to note the error on your file, actually reaching a human matters. There's a demo video at https://youtu.be/vwA1GGuV83Y that shows how it works. I used it when my adjudication was dragging on and got connected to an agent same day after days of failed attempts on my own.
0 coins
The Boss
AuthorHadn't heard of this, checking out that video now. If it means I can actually talk to someone about the duplicate without spending another two hours on hold I'm definitely willing to try it.
0 coins
Daniel Washington
Skeptical of these services generally but I've seen a few people on this forum say it worked for them. If the alternative is never getting through at all it makes sense.
0 coins
Aurora Lacasse
Claimyr worked for me when I had an overpayment notice I needed to dispute. Got connected within a couple hours. Way better than my previous attempts.
0 coins
Anthony Young
Duplicate job contact entries come up more than people realize and most agents have a pretty set way of handling it. When an agent can annotate your account with an acknowledged clerical error, it essentially takes the duplicate off the table as evidence of intentional misreporting. What you want to tell the agent specifically: the week ending date of the affected certification, the employer name that was duplicated, and that you're requesting a supervisory note on the file. Some agents will also suggest you submit a corrected job search log via the message center as an attachment to back it up.
0 coins
The Boss
AuthorSuper helpful breakdown. So I should specifically ask for a supervisory note, not just report the error generally?
0 coins
Evan Kalinowski
Asking for the note to be added is the difference between it being handled and just being acknowledged. Some agents are great about this automatically but it's worth asking explicitly.
0 coins
Charlotte White
Had an adjudicator tell me once that written documentation attached to the account carries more weight than just a phone note. So doing both - phone call plus a message center message - is the safest approach.
0 coins
Admin_Masters
okay so honest question - does DES even cross-check your job search contacts against each other within the same week? like does the system catch duplicates automatically or only if a human reviews it
0 coins
Oscar Murphy
The CACTUS system itself doesn't have an automated duplicate-checker that blocks submission - that's why OP was able to submit it in the first place. Human reviewers during audits or adjudication would catch it though.
0 coins
Victoria Charity
Random audits happen and job search logs are definitely something they look at. Not worth leaving a known error uncorrected.
0 coins
Admin_Masters
gotcha so it's more of a manual review risk than an automatic flag thing
0 coins
Matthew Sanchez
My first week on UI I submitted my certification and panicked because I thought I'd made an error too, turned out I hadn't but the anxiety of not being able to edit a submitted form is REAL. The locked certification thing should have a correction process built in, it's such an obvious need. Anyway - for your actual question, the message center in CACTUS under the 'Contact Us' section is worth using even just to create a written record. I sent a message about my situation and got a written reply back within about four business days.
0 coins
The Boss
AuthorFour business days is actually not terrible for a written response. Going to send something through there today in addition to trying to get through by phone.
0 coins
Jasmine Quinn
The message center is slept on honestly. People focus so much on the phone that they forget there's a paper trail option sitting right there in the portal.
0 coins
Nora Bennett
Three job contacts weekly is the standard requirement for most claimants. If you only have two valid ones for that week because of the duplicate, there's technically a shortfall. BUT - and this matters - if you can document that you did in fact make three separate contacts and the duplicate was a data entry mistake, the underlying compliance is there. The issue is proving it. That's why having the actual employer info for a third real contact you made that week would be huge. Did you actually make a third separate contact that week that just isn't logged?
0 coins
The Boss
AuthorYes! That's the thing, I actually did make a third contact that week at a different company. I just entered the wrong one twice by mistake. So the contacts were actually there, I just logged one of them incorrectly.
0 coins
Nora Bennett
That changes everything. You have grounds to submit a corrected log showing all three actual contacts. The duplicate wasn't because you only made two contacts, it was a transcription error. Explain that clearly when you reach an agent.
0 coins
Ella Thompson
This is the key piece of info. You did the job search, you just mis-entered it. Document that third real contact with any evidence you have - email confirmation, application receipt, anything.
0 coins
JacksonHarris
Adding another Claimyr mention because it's genuinely relevant here - once you get through to an agent via claimyr.com, have all your info ready: week ending date, name of the duplicated employer, and the name of the actual third employer you forgot to include. Agents can process corrections faster when you're organized. The video at https://youtu.be/vwA1GGuV83Y shows the callback setup which saves you from sitting on hold at all.
0 coins
Daniel Washington
The organized call prep advice is solid regardless of how you get through. Agents have limited time per call and knowing exactly what you need to say speeds everything up.
0 coins
Charlotte White
Bookmarking that link for when I inevitably need to call DES again. Hold times lately have been brutal.
0 coins
Aurora Lacasse
Something worth knowing for future certifications - when entering job contacts, Arizona DES wants you to include the method of contact (online application, email, in-person, phone call), the contact name or HR department, and the position applied for. If any two entries share the exact same employer AND method AND date, that's when reviewers flag it as a potential duplicate. Having slightly different positions or contacts at the same company on different dates is usually fine.
0 coins
The Boss
AuthorGood to know going forward. Mine was definitely an exact duplicate - same everything. No question it was an error.
0 coins
Evan Kalinowski
The specificity of the contact method field is something a lot of people overlook. 'Applied online' and 'submitted resume via email' to the same company on the same day can legitimately be two separate contacts if the positions were different.
0 coins
Ryan Andre
Worth keeping a personal spreadsheet of your weekly contacts before you enter them into CACTUS. Copy-paste errors go way down when you're working from a separate tracking doc.
0 coins
Victoria Charity
Just want to add - don't stop filing your weekly certifications while you're trying to get this resolved. Some people assume they should wait to file until the previous week's issue is sorted but that just creates more problems. Keep filing on schedule and document the correction attempt separately.
0 coins
The Boss
AuthorWas actually wondering about this. Good call, I'll keep filing normally.
0 coins
Jasmine Quinn
Pausing certifications is one of those things people do thinking it protects them but it actually just delays payments and can complicate things further. Always keep filing.
0 coins
Oscar Murphy
Agreed completely. Missing a certification deadline is a separate issue that's harder to fix than a job search log correction.
0 coins
Daniel Washington
Had a similar panic moment when I thought I'd duplicated an entry but it turned out I'd just entered two contacts at the same company for different positions on different days, which was fine. DES actually allows multiple contacts at the same employer if they're genuinely different. So if yours was truly the same position, same date, same contact - that's the duplicate scenario. If any detail legitimately differs, it might not be an issue at all.
0 coins
The Boss
AuthorMine was definitely the exact same entry twice, same date, same position title, same everything. No wiggle room on this one being a true duplicate.
0 coins
Nora Bennett
Even so, you're in decent shape because you have a third real contact to document. The question is just how to get it on record officially.
0 coins
Ryan Andre
CACTUS message center route for the correction: go to your account, look for the 'Contact DES' or 'Message Center' option, and write something like 'Correction needed for week ending [date] - job search log contains duplicate entry for [employer name]. Actual third contact was [third employer name, date, method]. Requesting annotation to reflect accurate job search activity.' Keep it factual and brief. Attach anything you have showing the third contact.
0 coins
The Boss
AuthorThis is exactly the kind of template I needed. Going to draft this out today.
0 coins
Charlotte White
Specific and professional tone is the right call for these messages. The agents reading them deal with a lot of vague or emotional messages so a clear factual one stands out.
0 coins
Jasmine Quinn
Screenshots of job applications submitted, confirmation emails, even LinkedIn connection requests can serve as documentation for a job contact. Gather whatever you have.
0 coins
Ella Thompson
I found Claimyr useful when I had a job search discrepancy on my account that needed an agent to manually review and correct. Got connected through claimyr.com and the agent was able to look at my certification, acknowledge my explanation, and add a correction note in about fifteen minutes. For anything involving manual annotation of your account this is exactly the kind of situation where reaching a live agent is worth it.
0 coins
Daniel Washington
Fifteen minutes to resolve something that could have dragged on for weeks if unaddressed - that's the value of actually getting through vs. leaving messages that may or may not get seen.
0 coins
Aurora Lacasse
Manual account corrections are one thing the message center can't always handle as cleanly as a live agent. Good reminder.
0 coins
Charlotte White
One more thing - when you do reach an agent, ask them to verify after the call that your account shows the correction note was added before you hang up. Some agents are great about confirming this, others forget. You have every right to ask them to read back the note they just added.
0 coins
The Boss
AuthorReally practical advice, wouldn't have thought to ask for confirmation before ending the call.
0 coins
Anthony Young
Ask for the agent's name or ID number too if they'll give it. Some won't but it's worth asking because it ties the annotation to a specific interaction if you ever need to reference it.
0 coins
Evan Kalinowski
Agent IDs aren't always given out but the date and approximate time of the call is usually enough to track the interaction in DES records if needed.
0 coins
Jasmine Quinn
Real talk this whole situation is way more stressful than it needs to be because DES made it impossible to self-correct a certification. Every other online form in existence has an edit option before final processing. The fact that CACTUS locks everything the second you submit creates so many unnecessary calls and corrections that agents have to process manually. Such a waste of everyone's time.
0 coins
Admin_Masters
Hard agree, an edit window of even like 24 hours before the certification fully processes would solve so many problems
0 coins
Victoria Charity
The system was designed a long time ago and hasn't kept up with basic UX standards. People make data entry errors constantly, it's completely normal.
0 coins
Oscar Murphy
Frustrating as it is, working within the constraints is the only option right now. The correction process via phone or message center exists specifically because they know the locked submission system causes errors.
0 coins
Matthew Sanchez
OP just want to check in - did you end up getting through to anyone or get a response from the message center? Curious how this resolved since I had a mini version of the same scare.
0 coins
The Boss
AuthorUpdate: sent the message center request with my documentation and also got through via phone the next morning. Agent added a correction note, confirmed my third contact was on file, and said the duplicate shouldn't cause any payment issues. Ended up not being a big deal once an actual human looked at it, but the anxiety was real while I didn't know.
0 coins
Matthew Sanchez
So glad it worked out. The 'submit and immediately panic' experience is way too common with this system.
0 coins
Nora Bennett
Good outcome. This thread is actually a solid reference for anyone else who hits the same issue since the correction process isn't documented anywhere obvious.
0 coins
Jeremiah Brown
Late to this thread but adding a data point: used Claimyr about a month ago specifically for a job search log issue on a past certification and it worked well - claimyr.com is the site. The callback system meant I wasn't glued to my phone waiting for a hold queue to move, just went about my day and got the call when an agent was available. For anyone finding this thread later while trying to fix duplicate job contact on DES weekly certification and hitting phone walls, that's worth knowing about.
0 coins
Daniel Washington
The callback vs. sitting on hold distinction is a bigger quality of life difference than it sounds when you're stressed about a claim issue.
0 coins
Ryan Andre
Useful for anyone who searches this topic and lands here. The combination of message center for written record plus Claimyr for live correction is probably the fastest path through this.
0 coins
Anthony Young
Summary for anyone finding this thread later: submitted weekly certifications on CACTUS cannot be edited by the claimant. A duplicate job contact entry leaves you technically short on the three-contact weekly requirement. The fix is to contact DES directly - either via the message center to create a written record or by phone to get a correction note added to your account. Have your week ending date, the duplicated employer name, and your actual third contact documented before you make contact. Getting ahead of the error proactively is much better than waiting to see if anyone notices it.
0 coins
Evan Kalinowski
Solid summary. The proactive vs. reactive point is crucial - this kind of error is very fixable before it becomes an adjudication issue but becomes much harder to address after a determination is made.
0 coins
Charlotte White
Pinning this in my head for reference. Job search log errors are more common than people admit and knowing the correction path in advance is genuinely useful.
0 coins
Jasmine Quinn
This thread should honestly be in a FAQ somewhere. The locked submission plus the three-contact requirement creates a very specific and common anxiety point that the DES website does not explain at all.
0 coins