Weekly certify unemployment - NYSDOL process explained
My weekly certifications have been a complete mess lately and I can't figure out what I'm doing wrong. Background: I was laid off from my warehouse job in February, got approved for UI benefits around mid-March, and I've been trying to weekly certify unemployment ever since. The first two weeks went fine - logged into my Unemployment Services account, answered the job search questions, confirmed my earnings, submitted. Done. But starting week three, every time I hit submit on my weekly claim, it just... hangs. The spinning wheel goes forever and then I get a generic error message that doesn't tell me anything useful. I've tried Chrome, Firefox, even dusted off Edge. Cleared my cache twice. Same result every single time. My job search log is completely up to date - I've been applying to places like NYSDOL requires, logging employer names, contact info, dates, all of it. I'm worried that if I can't get the weekly cert submitted, I'll lose my benefits entirely or trigger some kind of adjudication. Has anyone hit this technical wall with the weekly certification page? Is there a way to certify over the phone instead? I'm going on week two of this problem and my next rent payment is coming up fast.
86 comments

Natasha Volkova
Claimyr is worth trying here - it waits on hold with NYSDOL for you so you end up talking to a live agent, and an agent can manually process your weekly certification over the phone when the online portal is acting up. Check out claimyr.com and there's a demo video at https://youtu.be/Rdqa1gKtxuE so you can see exactly what it does before you try it. My portal had a similar freeze issue a couple months back and after burning two full days trying to get through the phone lines, I went the Claimyr route and finally got an agent who pulled up my claim and pushed the cert through on their end.
0 coins
Javier Torres
Two days on the phone lines - that tracks completely with my experience. The hold times for NYSDOL have been brutal this spring.
0 coins
Oliver Zimmermann
AuthorMy situation is basically exactly what you described with the portal freezing. Really considering trying Claimyr at this point since I've got nowhere else to turn on this.
0 coins
Emma Davis
Manual processing over the phone is actually an official option NYSDOL has, most people just don't know about it. An agent can enter your cert answers directly into the system.
0 coins
CosmicCaptain
Your error on the submit page - does it give you any error code at all, even a string of numbers? The NYSDOL portal has a few different failure modes and some are fixable on your end without calling anyone. The spinning-then-generic-error thing usually means either a session timeout mid-submission or a data validation conflict somewhere in your answers. Try this: before you start filling out your weekly cert, open the page, then immediately log out and log back in to refresh your session token. Then fill everything out quickly without pausing more than a minute between screens. Sometimes the system logs you out silently in the background while you're still typing and the submit just fails quietly.
0 coins
Oliver Zimmermann
AuthorNo error code at all, just 'an error occurred, please try again later' - which tells me nothing. Will absolutely try the fresh login trick though. Hadn't thought of the session timeout angle.
0 coins
Malik Johnson
Had the exact same generic error message for a week straight. Fresh login did not fix mine personally - ended up being something on NYSDOL's backend that resolved on its own after about 10 days.
0 coins
CosmicCaptain
Backend issues do happen, especially after NYSDOL pushes a system update. If the fresh login doesn't work after two or three tries over different days, that's probably what's happening here and you do need an agent to intervene.
0 coins
Isabella Ferreira
The phone certification option is real but the number matters - you want the Telephone Claims Center at 888-209-8124. When you get the automated system, there's a path through the menu that lets you certify your weekly claim by phone using your PIN. You set up your PIN when you first filed, so hopefully you remember it. If you don't have your PIN or never set one, that's a separate headache because you'd need to verify your identity again.
0 coins
Oliver Zimmermann
AuthorPIN - I genuinely cannot remember if I set one. I think I did during the initial filing but I'm not 100% sure. Guess I'll find out when I call.
0 coins
Ravi Sharma
Worth writing down that PIN somewhere safe once you recover it. I lost mine twice and verifying identity over the phone takes forever.
0 coins
Isabella Ferreira
Your PIN is usually 4 digits you created during the initial claim setup. If you blank on it, the automated system does have an option to reset it, but yeah, you'd need your SSN and claim ID handy.
0 coins
Freya Thomsen
The 888 number works for phone cert but be warned the hold times to reach an actual person if something goes wrong during the automated cert are rough. Early morning is the only sane time to call.
0 coins
Omar Zaki
Are you answering the availability and job search questions exactly the same way each week? Because my claim went into adjudication after I changed how I answered the 'were you able and available to work' question - I said no one week because I had a dentist appointment and panicked about it. The system flagged that cert and held my payment for three weeks while they reviewed it. Turned out the dentist appointment didn't make me unavailable at all, I just didn't understand the question properly.
0 coins
Oliver Zimmermann
AuthorMine have been consistent - I've been answering yes to able and available every week because I genuinely have been. So I don't think that's what triggered the technical error but I'm glad you mentioned it because I hadn't even considered how those answers affect adjudication risk.
0 coins
AstroAce
My first few certs I was so stressed about answering wrong that I'd re-read every question three times. The 'able and available' one trips a lot of people up - a single doctor's appointment doesn't make you unavailable, it has to be something that would prevent you from accepting full-time work if it were offered.
0 coins
Omar Zaki
Your experience with the dentist thing is super common based on what I've read in this forum. NYSDOL's question wording isn't great - 'able and available' sounds like you need to be sitting by the phone 24/7 which isn't what it means at all.
0 coins
Chloe Martin
Weekly certification timing is something a lot of people miss when they're new to UI - your cert window opens Sunday at midnight and closes Saturday at midnight for the previous week. If you try to certify outside that window for the wrong week, the portal sometimes throws an error that looks like a technical problem but is actually just a timing issue. Double check that you're certifying for the correct week and within the open window.
0 coins
Oliver Zimmermann
AuthorWindow is definitely open - I'm trying to certify within the right week. But I appreciate you flagging that because I had no idea there was a hard cutoff on Saturday.
0 coins
Diego Rojas
What happens if you miss the Saturday cutoff? My first cert I totally missed the window by a day and I panicked. Ended up needing to contact NYSDOL to have them manually open the cert for that missed week - took a while but they did fix it.
0 coins
Chloe Martin
Missing the window does not automatically end your claim, but you do need to contact NYSDOL to get a late certification processed. They can accommodate it but there's usually a waiting period before the payment releases for that week.
0 coins
Javier Torres
Had no idea about Saturday midnight being the cutoff. I've been certifying Sunday afternoons thinking I was fine - which I was, but that's because I was certifying for the right week. If I'd been a week off I would have been right at the edge.
0 coins
Anastasia Sokolov
The job search requirements tied to your weekly cert are worth double checking too. As of 2025, NYSDOL requires 3 job search activities per week for most claimants - if you're under that threshold and your answers reflect it, the cert can get flagged or even trigger an automatic disqualification review. The activities have to be legitimate contacts too, not just browsing a job board. Applying to a position, attending a job fair, reaching out to an employer directly - those count. Just looking at listings doesn't.
0 coins
Oliver Zimmermann
AuthorThree activities per week - yes, I've been hitting that. I've been keeping a detailed log with employer name, position, date, and how I applied. So that part should be fine.
0 coins
Sean O'Donnell
My log format was wrong apparently - I was writing really brief entries and when NYSDOL audited my job search activities they asked for more detail. Now I include the job listing URL when possible, the method of contact, and a contact name if I have one.
0 coins
Anastasia Sokolov
Your log format matters more than most people realize. NYSDOL can audit job search records going back several weeks and if the entries are too vague they may deny that activity as valid. The more detail the better.
0 coins
Zara Ahmed
Does applying on Indeed count? I've been using Indeed for most of my applications and I wasn't sure if that was considered a 'direct' enough contact.
0 coins
Anastasia Sokolov
Applying through Indeed absolutely counts as long as you log the specific employer and position, not just 'applied on Indeed.' The platform doesn't matter, the contact with an employer does.
0 coins
StarStrider
Claimyr got me talking to an NYSDOL agent in one shot when I had a frozen cert situation almost identical to yours. My weekly certification wouldn't submit for 11 days and I was convinced my claim was going to close out. The agent she reached confirmed my cert answers over the phone and manually entered that week's certification while I was on the line. Payment showed up two days later.
0 coins
Oliver Zimmermann
Author11 days of a frozen cert - that is exactly the kind of thing I'm afraid of. Really glad to hear the manual entry route actually works and payment comes through normally afterward.
0 coins
Luca Esposito
Manual cert by phone releasing payment on the normal schedule is good to know. I'd assumed that any deviation from online submission would delay things further.
0 coins
StarStrider
My payment came through on the standard schedule after the agent processed it. The manual entry goes into the same system as online submissions so there's no extra delay once it's in.
0 coins
Malik Johnson
Had a stretch where my portal was broken for two weeks and NYSDOL's website status page showed nothing wrong, as if everything was totally fine. The frustrating part is that some people's accounts were affected and others weren't - it seemed random based on what region your employer was in or something like that. Eventually my account just started working again with no explanation or notice from NYSDOL.
0 coins
Oliver Zimmermann
AuthorRandom by region - that would explain why I can't find anyone else locally complaining about the same issue right now. If it's patchy it might not show up on any status page.
0 coins
Malik Johnson
My neighbor filed around the same time as me and her account worked fine the whole time mine was broken. Same browser, similar claim type. Completely random.
0 coins
Emma Davis
The NYSDOL portal has historically had patchy outages that don't get acknowledged on their status page. It's genuinely one of the more frustrating aspects of the system.
0 coins
Freya Thomsen
Something that helped me when I was having online cert issues - try accessing your Unemployment Services account from a different network entirely, like your phone's data instead of your home wifi. Some ISPs have routing issues with the NYSDOL servers specifically and switching networks resolves it. Sounds dumb but it fixed mine immediately.
0 coins
Oliver Zimmermann
AuthorDifferent network hadn't even occurred to me. Trying my phone's hotspot right now actually - will report back.
0 coins
CosmicCaptain
Network routing issues with state government servers are a real thing, especially if your ISP uses certain upstream providers. It's not a common fix but when it works it feels like magic.
0 coins
Freya Thomsen
Mine was an ISP routing problem - switched to mobile data and the submit went through on the first try after days of failures. Worth the 30 seconds it takes to try.
0 coins
Ravi Sharma
Your question about losing benefits if you can't submit - there's a protection built in here that most people don't know about. If you can demonstrate you made good-faith attempts to certify during the open window and had technical issues, NYSDOL can process a late cert without penalizing you. The key is documenting your attempts: screenshot the error messages, note the dates and times you tried, and have that ready when you contact them. It won't work if you just say 'I tried and it didn't work' with no evidence.
0 coins
Oliver Zimmermann
AuthorScreenshots of the error - I should have been doing that from the start. Going to take them on every attempt from here on out. Really useful to know that good-faith effort has some protection.
0 coins
Zara Ahmed
Had no idea that documentation of the error matters for the late cert process. I went through something similar and just explained it verbally to the agent - luckily they took my word for it but I didn't have any screenshots.
0 coins
Ravi Sharma
Verbal explanation sometimes works if the agent is sympathetic and your claim history is clean, but documentation makes it much harder for NYSDOL to push back. Any evidence of a system error on their end also helps since it shows the problem wasn't your failure to try.
0 coins
Javier Torres
The standby status option is something worth knowing about if your situation changes - if you're on a temporary layoff and your employer expects to bring you back, you can be placed on standby and your job search requirements are waived. But you still have to weekly certify even on standby, which confuses a lot of people. The cert just looks slightly different and you won't be asked about your job search activities.
0 coins
Oliver Zimmermann
AuthorStandby doesn't apply to my situation since it looks like a permanent layoff, but that's genuinely useful context I didn't have. Wouldn't have known the cert is still required on standby.
0 coins
Javier Torres
Your case sounds like a straight regular UI claim which makes the job search logging and cert submission the main things to stay on top of. Standby is its own weird lane.
0 coins
Sean O'Donnell
My layoff was supposed to be temporary and I didn't apply for standby status, so I did all the job search activities for three months before my employer confirmed they weren't bringing anyone back. Wish I'd looked into standby earlier.
0 coins
AstroAce
My weekly cert had a similar submission error last fall and what finally got it resolved was asking the agent a very specific question - I asked them whether my account had any holds or flags on it that weren't visible to me in the portal. Turned out there was an identity verification flag on my account from a routine check that I had no idea about. It wasn't blocking my claim status display, just quietly preventing cert submissions. The agent cleared it in about 10 minutes once they found it.
0 coins
Oliver Zimmermann
AuthorHidden flags not visible in the portal - that is a genuinely terrifying possibility I hadn't thought of. That's actually a great specific question to lead with when I get an agent on the line.
0 coins
AstroAce
Claimyr is what finally got me to that agent after I couldn't get through on my own - my situation had been dragging for over a week at that point and I really needed to talk to someone who could actually see my account details.
0 coins
Emma Davis
Invisible account flags are more common than NYSDOL acknowledges publicly. The ID verification ones get triggered by mismatches in your filing info and they don't generate a notice to the claimant, they just sit there quietly breaking things.
0 coins
Malik Johnson
My invisible flag was different - it was a wages crossmatch issue where NYSDOL's records and my employer's reported wages were slightly off. Same result though: cert submissions failing silently with no explanation in the portal.
0 coins
Zara Ahmed
Does anyone know if there's a time limit on how long you can be in this broken-cert situation before NYSDOL automatically closes your claim? I've been following this thread because I'm starting week three of my own portal issues and I'm getting really scared.
0 coins
Isabella Ferreira
Your claim won't auto-close immediately but each uncertified week is a week you're not getting paid, and if you go long enough without any activity NYSDOL can flag the claim as inactive. Three weeks is definitely getting into territory where contacting them directly is urgent.
0 coins
Anastasia Sokolov
The inactive claim concern is real but NYSDOL does have a process for reactivating claims when there's documented technical issues. The bigger risk is letting it go too long without attempting to contact them - that makes the case for good-faith effort harder to make.
0 coins
Zara Ahmed
Three weeks and counting on my end - going to try to get through today. This thread has been genuinely helpful for knowing what to ask about.
0 coins
Sean O'Donnell
My weekly cert submissions started failing right after I reported part-time earnings for the first time. The earnings entry section of the cert has its own validation and if you enter earnings incorrectly - like putting gross instead of net or entering the wrong pay period - it can cause the whole submission to fail. The error message won't tell you which field caused the problem.
0 coins
Oliver Zimmermann
AuthorPart-time earnings aren't in my situation since I haven't worked at all since the layoff, so that one probably isn't the culprit for me. But flagging it here because I'm sure someone reading this thread has exactly that problem.
0 coins
Sean O'Donnell
NYSDOL wants gross earnings for the week they were earned, not the week you got paid - that's a really common entry mistake that breaks cert submissions for people with variable hours.
0 coins
CosmicCaptain
The gross vs. net distinction trips people up constantly. NYSDOL's earnings reporting instructions aren't prominently displayed on the cert page either so it's easy to guess wrong.
0 coins
Luca Esposito
Appeals information might be relevant here if the worst happens - if your claim gets disqualified because of missed certs due to this technical issue, you have 30 days from the determination date to file an appeal. The appeal process is handled by the Unemployment Insurance Appeal Board and it's separate from NYSDOL. You'd need to document that the missed certs were due to a portal error, not intentional non-compliance.
0 coins
Oliver Zimmermann
Author30 days from determination date for the appeal - noting that down just in case. Really hoping it doesn't come to that but it's good to know the option exists and what the timeframe is.
0 coins
Luca Esposito
Your documentation of error messages and attempt dates would be exactly the kind of evidence that supports an appeal based on technical issues. Appeal Board decisions do sometimes go in the claimant's favor in these situations.
0 coins
Ravi Sharma
Appeal timelines are strict - 30 days is not a suggestion and missing that window basically forecloses the appeal route. If a disqualification notice arrives in your Unemployment Services account, that date starts the clock immediately.
0 coins
Emma Davis
The difference between a technical portal issue and an adjudication hold is worth clarifying here because they look similar from the claimant's side but are very different situations. A tech error means the system is failing to accept your submission - your claim is otherwise fine. An adjudication hold means your claim has an open issue that needs resolution before benefits can pay. Both can produce cert submission failures but the solutions are completely different.
0 coins
Oliver Zimmermann
AuthorThat distinction is really helpful. From what I can tell in my portal there's no adjudication notice or pending issue shown anywhere, which makes me think this is a pure tech problem - but I won't know for sure until I get an agent to actually look at the account.
0 coins
Emma Davis
An agent seeing your account directly is the only reliable way to tell them apart. The claimant-facing portal often doesn't display adjudication holds in an obvious way, which is part of why they catch people off guard.
0 coins
Omar Zaki
My adjudication hold showed as a 'pending' status on my payments page but nothing on the cert page - I had no idea they were related until an agent explained that the hold was what was blocking my cert submission.
0 coins
Diego Rojas
Claimyr sorted out my phone situation when I had an adjudication issue on a cert - the hold times I was hitting on my own were two and three hours and I'd gotten disconnected twice already. After using Claimyr I ended up talking to an agent who could actually see the flag on my account and walked me through what I needed to send in to clear it. The whole call took maybe 25 minutes once I was actually talking to someone.
0 coins
Oliver Zimmermann
AuthorTwo to three hour holds followed by getting disconnected - honestly that's the part I've been most dreading about calling NYSDOL directly. If that's what I'm facing it makes the Claimyr route more appealing.
0 coins
Diego Rojas
My adjudication situation cleared up faster than I expected once the agent understood what was going on. The hard part was just getting to that agent in the first place.
0 coins
Zara Ahmed
Three disconnections on my own attempts before I gave up. I thought I was just unlucky but sounds like that's pretty standard for NYSDOL phone lines right now.
0 coins
Nia Thompson
My browser's autofill was actually causing my cert submissions to fail - the autofill was populating fields with old data in the background, including a phone number field it shouldn't have been touching, and that invalid data in a hidden field was breaking the validation on submit. Turning off browser autofill completely for the NYSDOL site fixed it instantly.
0 coins
Oliver Zimmermann
AuthorAutofill hadn't even entered my mind as a possible culprit. Disabling it for the NYSDOL site is a super easy thing to try before making any phone calls. Doing it now.
0 coins
Nia Thompson
The cert form has a lot of fields and browser autofill gets aggressive with government forms specifically. Disabling it site-by-site is usually an option in your browser's settings under privacy or autofill management.
0 coins
CosmicCaptain
Autofill interference with form validation is a genuinely underappreciated bug source. I'd actually add this to the list of first things to try before the fresh login trick I mentioned.
0 coins
Mateo Rodriguez
Has anyone had the weekly cert form just not load at all? Mine doesn't even get to the submission stage - clicking the cert link in my Unemployment Services account takes me to a blank page. Different browsers same result. I see the original poster is at least getting the form itself, which makes me think mine might be a different issue entirely.
0 coins
Isabella Ferreira
Blank page on cert load is usually a session or permissions issue in the account itself. Try logging into your Unemployment Services account, going to your profile settings first, then navigating to the cert from there - sometimes the routing matters.
0 coins
Nia Thompson
Had the blank cert page for two days. Turned out my browser was blocking a script that the cert form needed to load - disabling strict content blocking in my browser settings fixed it.
0 coins
Mateo Rodriguez
Content blocking - didn't consider that. My browser security settings are pretty aggressive. Going to try relaxing them for the NYSDOL site and see if the page actually loads.
0 coins
Emma Davis
Blank cert page and submission failure on an otherwise-loading page are two distinct problems. If the form won't even load, the advice about session tokens and autofill likely doesn't apply - that's more likely a script or permissions block like these folks said.
0 coins
Aisha Abdullah
My Unemployment Services account showed my weekly cert as 'submitted' on my end but when I checked payment status a week later the cert wasn't reflected at all - the system had accepted my submission visually but it never actually recorded it on the backend. Had to refile that week's cert with an agent. So even if the submission 'works,' worth checking payment status to verify the cert actually landed.
0 coins
Oliver Zimmermann
AuthorSubmission appearing to go through but not actually recording - that is a horrifying possibility I hadn't thought of. Going to check payment status after every future submission as a sanity check.
0 coins
Aisha Abdullah
My cert showed 'processing' on my end for a week before I realized nothing was moving. Payment status is the real indicator of whether a cert took - if no payment is processing within a couple days of a successful cert, something went wrong.
0 coins
Anastasia Sokolov
This is a known NYSDOL portal issue where the UI system confirmation and the backend processing get out of sync. It's not super common but it happens enough that checking payment status post-submission is genuinely good practice.
0 coins