This is exactly what I needed to see! I've been pulling my hair out for the past week with the same issue after completing IDme verification. Got the "technical error" messages initially, then the username/password loop, and now I'm getting random "session timeout" errors. I tried all the browser troubleshooting steps multiple times with no luck. Reading through everyone's experiences here, it's clear this is a systemic issue with PA UC's backend not properly handling the IDme integration. The fact that so many people are experiencing identical problems after verification really shows how broken their system is. I'm definitely going to try the Claimyr service - at this point I'd rather pay a small fee than waste more weeks trying to get through their impossible phone system. Thanks Paolo for the detailed updates and everyone else for sharing your solutions. This thread is going to save me so much time and stress!

Just want to add my experience to this thread since it might help others - I had this exact same issue last month after IDme verification on PA UC. Like others mentioned, I went through the whole cycle: technical errors, then the username/password loop, then session timeouts. What I discovered is that if you try to log in too many times while your account is stuck in that "post-verification status," it can actually make the problem worse by triggering additional security flags. I learned this the hard way after spending 3 days trying different browsers and clearing cache over and over. The key things that worked for me: 1. STOP trying to log in for at least 24 hours once you realize it's the backend flag issue 2. Use Claimyr or somehow get through to a human rep (the automated system can't fix this) 3. When you do talk to a rep, specifically mention "post-verification status flag" - it helps them understand the issue faster Also want to echo what others said - this thread should be required reading for anyone doing IDme verification with PA UC. The amount of people dealing with this shows it's not a rare glitch, it's a systematic problem with their integration. Saved me weeks of frustration reading everyone's experiences here!

Update: I filed my claim yesterday selecting "Lack of Work" as the reason, and it went through without any weird questions about disciplinary issues! I reported my severance as a lump sum payment and noted it covers 6 weeks. The system calculated my weekly benefit rate at $600 and said I'd have approximately a 14-week deduction period before payments would begin. Thank you all for the guidance - you saved me from making mistakes that might have delayed my claim. I'll keep filing weekly claims and documenting my job search activities in the meantime. This process is definitely not intuitive, so I appreciate the help!

Congrats on getting your claim filed successfully! Just wanted to add a few tips from my experience with PA UC after a layoff: 1. Download the PA UC mobile app if you haven't already - it makes filing weekly claims much easier than the website 2. Keep a dedicated folder (physical or digital) with all your UC paperwork, confirmation numbers, and job search records. You never know when you might need them 3. During your deduction period, you might be tempted to skip the weekly filings since you're not getting paid - DON'T! Missing even one week can mess up your whole claim Also, 14 weeks seems like a long deduction period - double check that calculation if you can. Sometimes the system gets it wrong initially. Good luck with the job search!

I just wanted to add something that might help - when you're gathering information about your temp work wages, you can actually request a wage statement from PA UC that shows all the wages reported under your SSN. I learned this trick from a friend who works at the local CareerLink. You can call and ask for your "wage and benefit statement" which will show you exactly what employers have reported for you. This way you'll know for sure if you meet that 6x threshold before you even file. It can save you the anxiety of wondering whether you qualify. The number is the same one everyone complains about (the 888 number that never answers), but if you can get through, they can email or mail you this statement usually within a few days. Just another tool to help you feel more prepared before starting the application process!

I'm actually in a very similar situation - my benefits ran out in October 2023 and I've been doing a mix of freelance graphic design work and some part-time retail to survive. This whole thread has been incredibly enlightening! I had completely given up on the idea of reapplying because I assumed once your benefits were exhausted, that was it. Learning about the 6x rule and the hardship waiver option is huge. I'm definitely going to calculate my earnings from the past year and see if I can qualify. The job market in PA has been absolutely devastating - I've applied to probably 200+ positions and gotten maybe 5 interviews. It's crushing your spirit after a while. But seeing everyone's experiences here gives me hope that there might be another option to help bridge the gap while I keep searching. Thank you all for being so generous with sharing your knowledge and experiences - this community is a lifeline when the official systems feel impossible to navigate!

I'm really impressed by all the detailed advice and support in this thread! As someone who's dealt with unemployment appeals (though not with Amazon specifically), I want to emphasize something that several people touched on but is worth repeating: the referee's job is to determine if you were terminated for "willful misconduct" under PA law. The key word here is "willful" - it's not enough for Amazon to show you didn't meet productivity standards. They have to prove you DELIBERATELY failed to meet standards despite knowing what was expected and receiving proper warnings. With only one coaching session and no documented progressive discipline, they're going to have a really hard time proving willful misconduct. Also, @Malik Robinson, make sure you're prepared to explain the timeline of your medical issues in relation to your performance. If your back problems started affecting your work and you informed management but they failed to provide accommodations or consider your medical limitations, that could actually shift the burden back to them to show they acted reasonably. One last thing - don't be surprised if Amazon tries to settle or withdraw their opposition right before the hearing. Sometimes when they realize they don't have proper documentation, they'll back down rather than risk losing officially on the record. Either way, you sound incredibly well-prepared thanks to all the great advice in this thread!

I've been through this exact situation with Amazon! Was terminated from their fulfillment center in Allentown for "productivity issues" last year and successfully won my appeal. Here's the most important thing - Amazon's progressive discipline policy REQUIRES three documented coaching sessions before termination. If you only had one, that's a slam dunk policy violation. During my hearing, Amazon's lawyer brought stacks of productivity reports but when the referee asked for documentation of the required warnings, they had almost nothing. The referee specifically asked them to explain why they skipped their own disciplinary procedures and they couldn't give a good answer. For your hearing prep: - Request your complete personnel file immediately - Document every conversation you had about your back issues, even verbal ones - Print out Amazon's progressive discipline policy from the employee handbook - Prepare to ask THEM why they didn't follow their own three-step process The medical accommodation angle is huge too. Even without doctor's notes, your testimony about reporting limitations and being told to "deal with it" shows they failed their legal obligation to engage in interactive process. I was terrified going in but the referee was totally fair and professional. Got my decision in 10 days and received 7 weeks of backpay. You've got this - Amazon's own policies will work against them when they can't show they followed proper procedures!

This entire thread has been such a valuable resource! As someone who's brand new to the PA UC system after being laid off two weeks ago, I was starting to panic about some confusing messages on my own dashboard. Emma's story perfectly illustrates what so many of us go through - it's reassuring to see that the "expect payment" message during weekly certification really is the key indicator to trust, even when other parts of the system show conflicting information. The fact that she got paid even with the open issue still showing on the dashboard is both frustrating and comforting at the same time. It really highlights how unreliable their dashboard can be for tracking actual claim status. Thanks to everyone who shared their experiences and insights - this community is already proving to be invaluable for navigating PA UC's confusing system!

This thread has been incredibly helpful to read through as someone who's relatively new to dealing with PA UC! Emma's experience really shows how confusing their system can be - it's both frustrating and reassuring to see that the dashboard can show conflicting information while payments still go through normally. The consensus here about trusting the "expect payment" message during weekly certification over other dashboard elements is such valuable advice. I've been dealing with some similar inconsistencies in my own account and was starting to worry, but seeing everyone's real experiences and Emma's positive outcome gives me much more confidence. Thanks to everyone who takes the time to share their actual experiences rather than just speculation - it makes navigating this whole system so much less stressful when you know others have been through the same thing!