


Ask the community...
One thing - you still have to meet the job search requirements even for partial unemployment. Keep track of your work search activities because they can ask for your log anytime during certification.
Wait, really? I thought if you're still working even part-time you don't have to do job searches since you already have a job. Are you sure about the work search requirement for partial claims?
Actually, @NebulaNomad is right to question this. For partial unemployment in NY, you generally don't have to do work search activities if you're still employed by the same employer and expect to return to full hours. The work search requirement typically only applies if you're totally unemployed or if your partial work is expected to be permanent. @Avery Davis might be thinking of a different situation or state rules.
Just went through this exact same situation at my job! The key thing is to file online at labor.ny.gov and when you do your weekly certifications, always report your gross earnings (before taxes). The system will automatically calculate how much partial benefit you get. Also keep all your pay stubs - they sometimes ask for proof of your reduced earnings. The whole process was way easier than I expected once I actually started it. Good luck!
I've been helping people with ID.me verification issues for months now, and I want to add a few more troubleshooting tips that have worked for others: 1) Try using incognito/private browsing mode - this eliminates any browser extension conflicts, 2) If you're on mobile, make sure your phone's camera lens is clean (sounds obvious but you'd be surprised!), 3) For the selfie part, hold the phone at arm's length and look directly at the camera, not at your image on screen, 4) If you wear contacts, try without them as sometimes the reflection can interfere with facial recognition. Also, Pro tip: If you get through the document scan but fail at facial recognition, don't restart the whole process - you can usually just retry the selfie portion. The verification usually takes 2-3 business days to process once you successfully complete all steps, so factor that into your timeline. Hang in there - almost everyone gets through eventually!
Thanks for all these detailed tips! The incognito mode suggestion is really smart - I never would have thought about browser extensions causing issues. I'm definitely going to clean my camera lens too (you're right, it's probably obvious but easy to overlook when you're frustrated). Quick question - when you say the verification takes 2-3 business days to process after completing all steps, does that mean I won't be able to certify for benefits during that waiting period? Or can I still submit my weekly certification while it's processing?
I'm dealing with the exact same issue right now! Been stuck on the facial recognition part for 3 days straight. Reading through all these tips is super helpful - I had no idea about the VPN issue or using a dark surface for the ID scan. Going to try the phone + Safari + natural lighting combo tomorrow morning, and definitely turning off my VPN first. It's so frustrating that such an important process has so many technical glitches, but at least it sounds like most people eventually get through. Thanks everyone for sharing what worked for you - gives me hope I'll figure this out soon!
I feel your frustration! I went through this same nightmare about a month ago. One thing that really helped me was doing the verification early in the morning (around 8-9 AM) when their servers are less busy - I noticed way fewer glitches and timeouts compared to trying in the evening. Also, make sure your phone is fully charged and close any other apps running in the background to free up processing power. The combination of good lighting + clean camera + minimal background apps finally got me through after almost a week of failed attempts. You've got this - just stay patient and methodical with trying each tip!
Wow, this thread is incredible - thank you all for creating such a comprehensive troubleshooting guide! I've been banging my head against the wall trying to upload my documents for over a week now. Every time I try during regular hours, I get error messages or the upload just stalls out completely. I had no idea that timing could make such a difference, but reading through everyone's experiences, it makes total sense that the system would be overloaded during business hours when everyone's trying to access it. I'm definitely going to try the early morning approach (6:30am) this weekend using Chrome with cleared cache, PDFs under 5MB with descriptive names, and uploading one document at a time. Having the secure message center as a reliable backup option is such a relief too. It's honestly frustrating that we need to become system experts just to submit basic paperwork, but this community has turned an impossible task into something actually manageable. Will report back with results!
This thread has been absolutely amazing to follow! I'm brand new to dealing with unemployment claims and was feeling completely lost with the document upload process until I stumbled across this discussion. Reading through everyone's detailed experiences and solutions has been so much more helpful than anything on the official DOL website. The early morning timing strategy that keeps coming up (around 6-7am) is such a brilliant insight - I never would have thought that server load could affect upload success so dramatically, but it makes perfect sense when you consider how many people are probably trying to use the system during normal business hours. I'm planning to follow the exact same approach that's worked for Keisha and others: wake up early, use Chrome with cleared cache on my personal computer, convert everything to properly named PDFs under 5MB, and upload one document at a time. Having the secure message center under "My Messages" as a backup plan gives me so much peace of mind too. Thank you everyone for sharing such specific, actionable advice - this community is incredible for helping people navigate these frustrating government systems!
As someone who just went through this exact process last month, I want to add that keeping detailed records of every attempt is crucial! I created a simple spreadsheet tracking when I tried to upload (date/time), which browser I used, file sizes, and whether it succeeded or failed. This helped me identify patterns - like noticing that my afternoon attempts always failed while early morning ones worked. Also, if you do end up needing to call or use a service like Claimyr that Dylan mentioned, having this documentation makes the conversation much more productive. The agent could see exactly what I'd tried and immediately suggested solutions I hadn't considered. One more tip: if you're uploading paystubs, make sure they clearly show your employer's name and your full name - I had to re-upload some because the quality was too low to read the details clearly.
This is such smart advice about keeping detailed records! I wish I had thought of that from the beginning - I've just been randomly trying different things without tracking what worked or didn't. Creating a spreadsheet with date/time, browser, file sizes, and success/failure is brilliant for identifying patterns. I can already see how that would be incredibly helpful if I need to contact support or use a service like Claimyr. The tip about paystub quality is really important too - I bet a lot of upload "failures" are actually just documents that aren't clear enough to process properly. I'm going to start documenting everything from my next attempt onwards. Thanks for adding this organizational perspective to all the technical troubleshooting tips everyone has shared!
This thread is absolutely incredible - I can't believe how many of us are dealing with this exact same security question nightmare! I've been stuck on this maiden name issue for about a week now and was honestly starting to question my own sanity 😅 Reading through all these detective strategies has given me so much hope though! The suggestions about trying different capitalizations, hyphens, middle initials, birth years, professional names, and even religious/confirmation names are brilliant. I never would have thought to consider that my mom might have used her confirmation name or that I could have accidentally included extra details like birth years when I originally signed up. One angle I'll add to this amazing crowdsourced troubleshooting guide: if your mom ever used a shortened version of her name on some documents but the full version on others, try both! My mom's maiden name is "Elizabeth" but she went by "Betty" on a lot of informal paperwork, and I'm realizing I might have used the nickname version without thinking about it. I'm definitely making that systematic checklist everyone's talking about and working through every possible variation before attempting another phone call. It's absolutely ridiculous that we have to become genealogy researchers just to access our own benefits, but this community support is what's keeping me motivated! Thanks everyone for sharing your experiences and strategies - knowing we're all in this bureaucratic nightmare together makes it so much more bearable. I'll report back when I crack my personal security code mystery! 🙏💪
This thread has been such a lifesaver! I just created an account specifically to join this conversation because I'm dealing with the exact same maiden name nightmare 😭 I've been locked out for almost two weeks now and was honestly starting to think I was going crazy. The nickname suggestion you just made is GENIUS! My mom's legal name is "Margaret" but she's gone by "Peggy" her entire adult life, and I'm betting that's exactly what I entered when I signed up years ago without even thinking about the legal vs. common name difference. I'm so grateful for everyone sharing their detective strategies here - between all the suggestions (different spellings, capitalizations, hyphens, middle initials, birth years, professional names, confirmation names, and now nicknames) we've basically created the ultimate security question troubleshooting guide! It's completely insane that we have to become forensic genealogists just to update our bank info, but reading all these success stories is giving me hope that there's actually a light at the end of this bureaucratic tunnel. I'm definitely making my own systematic checklist and tackling this methodically tomorrow morning. Thanks for adding another brilliant angle to consider - the formal vs. nickname distinction could be the key for so many of us! 🙏✨
I'm going through this exact same issue and it's so frustrating! 😤 I've been trying to update my direct deposit for over a week now and keep getting that "mother's maiden name doesn't match" error. Reading through all these amazing responses has given me so much hope though! One thing I want to add that might help others: check if your mom ever used different versions of her name for different purposes. My mom used her full legal name "Patricia" on official documents but went by "Patty" socially and sometimes "Pat" professionally. I'm realizing I might have used one of the shortened versions when I quickly filled out the form years ago. Also, if your family is from a culture where names are structured differently (like having multiple middle names or family names), you might have entered a different combination than what's in their system. My mom has both her father's and grandfather's surnames in some old documents, so I'm going to try those variations too. I'm definitely going to try the systematic approach everyone's mentioned - making a list of every possible variation and working through them methodically. It's absolutely ridiculous that we have to become name detectives just to access our own benefits, but this community support is keeping me sane! Thanks everyone for sharing your experiences - it's so reassuring to know we're not alone in this bureaucratic nightmare! I'll update if I crack my personal mystery 🤞
This is such a helpful addition to all the strategies! The cultural naming structure point is really important - I hadn't thought about that at all! My family background is similar where there are multiple surnames and different naming conventions, so I might have gotten confused about which combination to use when I originally signed up. The Patricia/Patty/Pat example is perfect too - it's so easy to use whatever version of a name you're most familiar with in daily life without thinking about the "official" version. I'm definitely adding all the nickname/professional name variations to my list along with the other brilliant suggestions everyone's shared here. It's honestly wild that we've basically had to create a whole community research project just to figure out our own security questions, but I'm so grateful for threads like this! The systematic approach with a comprehensive list seems like the way to go - way less frustrating than just randomly guessing. Thanks for adding the cultural naming angle - that could be exactly what some of us need to consider. This whole thread has been like a masterclass in security question troubleshooting! Here's hoping we all crack our personal mysteries soon 🙌
Salim Nasir
I'm so sorry you're going through this - the stress of having benefits suspended during an investigation is absolutely brutal. I went through a similar situation about 18 months ago and it took roughly 6 weeks to resolve. What I learned is that being proactive really helps, even though the waiting is still agonizing. I'd recommend gathering ALL your documentation now - job search logs, bank statements, termination paperwork, any correspondence with employers - and send it certified mail even if they haven't specifically requested it yet. Also, if you haven't already, try to get through to someone on the phone to at least confirm what triggered the investigation. Like others mentioned, calling right at 8 AM seems to be the best time to actually reach a human. The system is frustrating but hang in there - legitimate claims do get cleared up, it just takes way longer than it should. Keep detailed records of every interaction and don't let them make you feel guilty for following up regularly. You deserve to know what's happening with your case.
0 coins
Isabella Brown
•Salim, thank you so much for the detailed advice and encouragement - it really helps to hear from someone who made it through this process. 6 weeks feels manageable compared to some of the longer timelines people have shared. I'm definitely going to take your advice about sending documentation proactively via certified mail. Better to have everything on file rather than waiting for them to request it piece by piece. The part about not feeling guilty for following up regularly really resonates with me - I keep second-guessing myself about whether I'm being too pushy by calling, but you're right that I deserve to know what's happening. I'll start the 8 AM calling schedule this week and put together my documentation packet this weekend. Thanks for reminding me that legitimate claims do get resolved eventually, even when the system feels completely broken.
0 coins
Yuki Kobayashi
I'm dealing with a fraud investigation right now too - just hit the 5 week mark yesterday. The uncertainty is absolutely crushing, especially when you know you did everything by the book. What's helped me mentally is setting up a routine around it rather than letting the anxiety consume me randomly throughout the day. I call every Tuesday and Friday at 8 AM sharp (seems to be the magic hour based on what everyone's saying), keep a spreadsheet tracking every interaction, and I've already sent them a comprehensive evidence packet via certified mail. The financial stress is real - I've had to ask family for help with rent which is humiliating when this whole thing shouldn't even be happening. But reading through all these experiences gives me hope that most legitimate cases do get resolved, even if it takes way longer than any reasonable person would expect. Stay strong and keep documenting everything - we'll get through this bureaucratic nightmare eventually.
0 coins