


Ask the community...
UPDATE: I finally got this resolved! For anyone else having this issue, here's what worked: I used the Claimyr service that someone mentioned above to get through to an actual person at DEO. The agent explained that my account was created during the pandemic and got stuck in the system update transition. They manually added a username to my account and sent a completely new password reset link to my email. I was able to claim my weeks that were pending and even got backpay for the ones I missed while locked out! Thank you to everyone who offered advice - this community is amazing!
This is such a relief to read! I've been dealing with the exact same issue for over a week now and was starting to panic about missing my claim deadlines. It's frustrating that DEO doesn't have clear instructions about this username requirement anywhere on their website - I've been going in circles trying to figure out what I'm supposed to do. Thank you @Aisha Khan for updating us with your solution, and thanks to everyone else who shared their experiences. It really helps to know we're not alone in this mess. I'm going to try the Claimyr service tomorrow since the phone lines have been impossible for me too. Hopefully they can get me sorted out quickly like they did for you!
@Yuki Sato I m'in the same boat as you! Just discovered this thread after being locked out for 5 days. The lack of clear communication from DEO about this username issue is absolutely maddening - how are we supposed to know what we don t'know?? I m'definitely going to try both the CareerSource office visit and the Claimyr service. It s'crazy that we have to jump through all these hoops just to access our own benefits. Thanks to everyone who shared their solutions here - this community is literally more helpful than the actual DEO website!
Congrats on getting it resolved! This is such a helpful thread - I'm bookmarking it in case I run into the same issue. The CONNECT system really needs a major overhaul, but it's good to know there are workarounds when these glitches happen. Thanks everyone for sharing your experiences and solutions!
Same here! I'm new to unemployment and was worried about what would happen if I ran into technical issues like this. It's reassuring to see that there are solutions and that the DEO agents can actually fix these problems when you reach them. This community has been so helpful - I never would have known about services like Claimyr or the reconsideration forms without reading through these discussions. Definitely saving this thread for reference!
This thread is a goldmine of information! I'm dealing with a similar CONNECT glitch right now where the system froze while I was uploading documents for my identity verification. When I logged back in, it shows my verification as "pending" but won't let me re-upload the documents or continue the process. Has anyone experienced this specific issue? I'm worried it's going to delay my whole claim. Based on what I'm reading here, it sounds like calling DEO directly might be my best bet, but I wanted to check if there are any other workarounds before I potentially wait on hold for hours.
I had the exact same identity verification issue! The system froze during my document upload and left me stuck in "pending" status. What worked for me was completely logging out of CONNECT, clearing my browser cache and cookies, then trying again with a different browser (I switched from Safari to Chrome). If that doesn't work, you can also try uploading documents in smaller file sizes - sometimes the system times out with larger files. But honestly, after reading this thread, calling DEO through Claimyr might save you more time in the long run. The verification delays can really hold up your whole claim process, so it's worth getting it fixed ASAP. Keep us posted on what works for you!
As someone who just went through this exact same nightmare last week, I can confirm that the system is absolutely broken by design. What worked for me was a combination of what others mentioned here - I had to wait the full 72 hours after ID.me verification, then use a completely different browser (Edge worked when Chrome and Firefox didn't), and create a super complex password. But the real kicker was that my account was still locked even after all that, and I had to get DEO to manually unlock it. The fact that they don't tell you when your account is locked is criminal. For anyone still struggling with this, document EVERYTHING with timestamps and screenshots - it helps when you finally get through to an agent. This system desperately needs a complete overhaul.
This is incredibly frustrating but so validating to read! I'm new to this whole unemployment process and was starting to think I was doing something fundamentally wrong with the CONNECT system. Your point about documenting everything with timestamps is brilliant - I wish I had started doing that from day one. It's honestly shocking that in 2025 we still have to deal with government systems this broken. Thank you for sharing your experience and the practical advice about trying Edge browser. Going to try that next along with the screenshot documentation approach.
This entire thread is a perfect example of why Florida's unemployment system is fundamentally broken. @Paolo Moretti I'm so glad you finally got through, but the fact that you had to use a third-party service just to contact DEO about THEIR system failing is absolutely insane. I've been helping people navigate CONNECT issues for over a year now, and the ID.me integration has made everything exponentially worse. The lack of clear communication about account locks, the hidden password requirements, the sync delays - it's like they designed this system to fail. What really gets me is that DEO knows these issues exist but does nothing to fix the root problems or even provide better error messages. Instead they just tell people to "keep trying" while their accounts get locked behind the scenes. For anyone reading this thread later: save yourselves the headache and assume your account will get locked if you have ANY issues after ID.me verification. Don't waste days trying technical fixes - go straight to getting DEO on the phone (however you can manage it) and have them manually verify everything. The system is broken, not you.
@Lim Wong You ve'hit the nail on the head! As someone completely new to this system, reading through all these experiences has been both enlightening and terrifying. It s'mind-boggling that a state unemployment system - something people rely on during their most vulnerable times - can be this dysfunctional. The fact that multiple people had to use third-party services just to contact the agency responsible for the broken system speaks volumes about how backwards this whole setup is. I m'just starting my unemployment claim process and honestly dreading the ID.me integration now. Should I expect my account to get locked and just plan accordingly? It seems like the normal "experience" is actually the broken one based on everyone s'stories here.
I'm experiencing this exact same login loop issue right now! It's so frustrating - I keep getting sent back to that warning page no matter what I try. I've been reading through all the suggestions here and it sounds like this is almost always caused by some kind of account flag that DEO doesn't bother to notify you about, which is absolutely ridiculous system design. I've already tried different browsers, clearing cache, using my phone instead of computer, and logging in at different times of day. Nothing has worked so far. Based on everyone's experiences here, it seems like I'm going to need to speak with a live DEO agent to get whatever flag is on my account cleared. I'm definitely going to look into that Claimyr service that several people mentioned - sounds like it could save me days of trying to get through on my own. Thanks to everyone who shared their solutions and experiences. It's really helpful to know this is a known issue and not something I'm doing wrong!
I went through this exact same nightmare about 6 weeks ago! That login loop is absolutely maddening - you keep thinking you must be doing something wrong but it's totally their broken system. I wasted almost 4 days trying every browser, device, and time of day before realizing it was an account flag issue. The complete lack of notification is infuriating - how are we supposed to know our account is flagged if they don't tell us anything? I ended up using a callback service similar to what others mentioned here and got through to a DEO agent who cleared some random "quarterly review" flag in about 2 minutes. Don't waste as much time as I did - if the basic troubleshooting isn't working after a day, you definitely need to talk to a live person. The system is just poorly designed and these flags happen all the time with no warning. Hope you get it sorted out quickly!
I'm going through this exact same login loop nightmare right now! Been stuck for 2 days and it's so frustrating. I've tried Chrome, Firefox, Safari, cleared all my cache and cookies, even tried from my phone and my work computer - nothing works. Just keeps bouncing me back to that warning page over and over. Reading everyone's experiences here, it's clear this is usually an account flag issue that requires talking to a DEO agent to fix. The fact that they don't send ANY notification when your account gets flagged is absolutely terrible - how are we supposed to know there's even a problem? I'm definitely going to try that Claimyr service that @Tami Morgan and others mentioned. At this point I've wasted so much time trying to fix this myself. Thanks everyone for sharing your solutions - it really helps to know this is a widespread issue with their system and not something I'm doing wrong!
Sophie Footman
Thanks for sharing this update! Good to know they're at least acknowledging the problem. I managed to get registered using the 'wrong address' method suggested earlier, but I'll pass this info along to my friend who's having similar issues.
0 coins
Zara Malik
I'm dealing with a similar issue but mine's a bit different - the system is showing my street name as "Main Street" when it should be "Main Ave". I tried the workaround of using their incorrect version but it's still not working for me. Has anyone had success with street name discrepancies specifically? I'm wondering if I should try going to a CareerSource center in person since the online fixes aren't working.
0 coins