


Ask the community...
Been through this exact same thing! I was so paranoid when I started my new job and saw the unemployment office contacted my employer. Turns out it's literally just a routine verification form - they're closing the loop on your claim to make sure you're not still collecting while working. My boss didn't even mention it to me, HR just handled it like any other paperwork. You're overthinking it (I did too!) but there's really nothing to stress about here.
I went through this same anxiety when I started my new position last year. The unemployment office sent a standard "Request for Separation Information" form to my employer, but it's literally just asking for basic employment verification - start date, wage, etc. My HR department told me they get these all the time and it's completely routine. They're not sharing details about your unemployment claim or making any judgments. It's just the state closing out your file to prevent overpayments. Your new employer won't think twice about it, trust me!
This thread has been so helpful! I'm dealing with a similar situation where my claim got flagged after a brief temp job, but reading through everyone's experiences makes me feel less alone in this mess. @Arjun Kurti I'm so glad you got your issue resolved! For anyone still struggling with holds, I wanted to add that I've found calling right when they open (8 AM) on Tuesdays gives you the best chance of getting through without waiting hours. Mondays are apparently their busiest day. Also, if you're having document upload issues like @Emma Johnson, try uploading from a computer instead of your phone - the mobile interface seems even more glitchy than the desktop version. The fact that so many of us are going through the same automated hold issue shows this is definitely a system problem, not individual mistakes. Hang in there everyone - it's frustrating but it does get resolved eventually!
@Maggie Martinez Thank you for sharing those calling tips! The Tuesday 8 AM advice is really valuable - I had no idea about the Monday rush. It s'honestly both reassuring and infuriating to see how many people are dealing with these same automated holds. The system clearly has some major flaws when legitimate claims keep getting flagged like this. @Arjun Kurti s success'story gives me hope though! I m currently'dealing with a similar situation where my claim got put on hold after reporting a short-term gig, so seeing that it can be resolved quickly once you get through to the right person is encouraging. Going to try the Claimyr service and your Tuesday morning calling strategy. Thanks for the solidarity - it really does help to know we re not'alone in this bureaucratic nightmare!
I just went through this exact same situation last month! My account was put on hold after I answered a questionnaire about a 3-week temp job I had already reported months earlier. It's so frustrating when you've done everything correctly and the system still flags you. What helped me was keeping detailed records of everything - screenshots of when I originally reported the employment, copies of all my weekly certifications, etc. When I finally got through to an agent (took me about 2 weeks of trying), having all that documentation ready made the conversation go much smoother. They were able to see that I had already properly reported everything and lifted the hold immediately. The agent explained that these secondary reviews are unfortunately common right now, especially if there's any gap or temporary work in your claim history. It's not that you did anything wrong - the automated system just gets confused and flags accounts for manual review. @Arjun Kurti I'm glad you got yours resolved so quickly! For anyone else dealing with this, don't lose hope. It's a pain but it does get sorted out once you reach the right person. The key is persistence and having your documentation organized when you finally get through.
@Dylan Evans This is such great advice about keeping detailed records! I wish I had thought to take screenshots when I originally reported my employment - that would have made things so much easier when I had to explain everything to the agent. Your point about the system getting confused "really" resonates with me. It s'wild that we have to deal with these glitches when we re'already stressed about unemployment. For anyone reading this who hasn t'had this happen yet - definitely screenshot everything and keep copies of your weekly certifications! You never know when the system might decide to flag your account for a review you ve'already been through. @Arjun Kurti s experience'and yours both show that persistence really does pay off, even though it shouldn t be'this difficult in the first place.
Just wanted to update everyone - the site is working for me now! Was able to log in and certify my weekly claim about 10 minutes ago. Seems like they fixed whatever server issues they were having. For anyone still having trouble, I'd recommend trying again now. If you're still getting errors, definitely try Eva's suggestions above - clearing cache and using incognito mode helped me earlier when it was partially working.
Just tried again after seeing these updates and it's working for me too! Was getting the same server connection errors all morning but just successfully logged in and certified. Thanks everyone for sharing the workarounds - definitely going to bookmark Eva's tips for next time this happens. The NY DOL really needs to invest in better infrastructure, these outages are way too frequent 😤
Same here! Just got through after trying all morning. Really appreciate everyone sharing updates - was getting super stressed about the deadline. @Eva St. Cyr your troubleshooting tips were clutch! Definitely agree they need better servers, this happens way too often 😮💨
also dont forget to certify every week going forward, not just the back weeks. i think the deadline is sunday but check your account
Just went through this exact same process last month! A few tips that helped me: 1) You can definitely claim all 6 weeks retroactively - that's what the system is designed for. 2) When you're filling out the weekly certifications, take your time with each one because you can't go back and edit them once submitted. 3) For the work search requirement, even if you didn't keep perfect records during adjudication, be honest about what you remember doing - checking job boards, updating your resume, etc. all count. 4) The first payment usually takes about 2-3 business days after you certify, but subsequent weeks are faster. Don't panic if there's a slight delay on the first one. You've got this!
StardustSeeker
The system is so rigged in favor of employers. They know most people can't afford lawyers to fight back so they just lie with impunity. Even if you win your unemployment case, there's rarely any consequences for them providing false information. It's infuriating but that's the reality.
0 coins
Paolo Marino
•Same thing happened to my sister last year. Employer claimed she stole money when she was actually laid off due to budget cuts. She won eventually but it was a nightmare.
0 coins
Kai Rivera
If you have clear documentation showing they told you it was performance-related and now they're claiming misconduct, that's strong evidence of inconsistent statements. Document everything - save those emails, keep copies of your termination paperwork, and write down dates and details of any conversations you remember. During the adjudication process, present this evidence clearly and chronologically. While suing for defamation is theoretically possible, it's expensive and hard to prove damages beyond the unemployment benefits. Your best bet is to focus on winning the unemployment case first - if you can show their story changed, the adjudicator will likely rule in your favor.
0 coins
Natasha Volkov
•This is really helpful advice. I'm wondering though - if I do win the unemployment case and can clearly prove they lied, would that strengthen any potential defamation case? It seems like having an official ruling that their statements were false might make it easier to prove they knowingly provided incorrect information.
0 coins