Technician helping troubleshoot Fire TV automation and Alexa routine issues for seniors

Steve H.

Reviewed for technical accuracy

Specialities: “high risk flag” verification pending triage, risk-based sign-in and fraud alerts, safe account access checks for seniors, VPN/IP/location change diagnosis.

When verification is pending because of a “high risk” security flag, check recent changes (VPN, new device, travel), cooldowns, and trusted sign-in methods before retrying

Technician avatar Technician
Hi! When you see “Verification Pending Due To High Risk Flag”, it usually means the system thinks the sign-in attempt is risky (not necessarily wrong). It can happen after a location/IP change, a new device, many retries, or a recent security update.

Trust moment: I don’t want you to keep trying over and over. Rapid retries can extend cooldowns and keep the risk flag active longer.

To help safely, tell me:
1) Which service is showing this (Microsoft, Google, Facebook, banking, email, etc.)?
2) Did it start today, or after an update / travel / new internet router?
3) Are you trying on a phone app, a laptop browser, or both?
Customer
It’s my email account. It suddenly said “high risk” and now it’s stuck on verification pending. I’m older and I get confused with these security screens. I tried a few times and now it’s not moving.
Technician avatar Technician
You’re not alone — these screens are stressful, especially when they appear without warning.

A “high risk” flag is often triggered by simple things like:
• signing in from a new browser or device,
• home Wi-Fi changing (new router, power outage, ISP change),
• using a VPN/proxy or privacy DNS,
• too many sign-in attempts or code requests.

Safe first question: did you recently change your password, add a new phone number, or turn on/off two-step verification (2FA)?
Customer
I changed my password last week because I got a warning email. Also my grandson helped me add an authenticator app on my phone. Since then I sometimes get codes, sometimes not, and now it says pending.
Technician avatar Technician
That explains a lot: a password change + new 2FA method often increases security checks for a while.

Trust moment: I don’t want you to remove your security methods in a panic. Removing phone/email recovery while the system is alert can make account recovery harder.

Let’s do calm, low-risk checks that only look at the environment (not the account):
1) Are your phone’s date/time set to automatic? Authenticator codes can fail if the clock is off.
2) Are you on your usual home Wi-Fi, or a different network?
3) Are you using any VPN, “security” browser, or strict tracking protection?
Customer
I’m on home Wi-Fi. No VPN, but my browser has tracking protection. My phone time might not be automatic. Also I keep switching between the laptop and the phone because I’m not sure where it wants me to finish.
Technician avatar Technician
That switching can accidentally look like suspicious activity (multiple sessions, different device fingerprints). It’s a very common senior pain point.

Here’s the safest approach: pick one device for your next attempt (phone OR laptop), and keep everything stable for that attempt — same network, no VPN, one browser.

Also, if your phone time isn’t automatic, authenticator approvals can be inconsistent. You don’t need to change anything yet — just check if “Set automatically” is enabled, then come back to the sign-in flow once.
Customer
I’m worried the “high risk” flag means someone is hacking me. Should I keep trying until it lets me in? I can’t lose my email.
Technician avatar Technician
I understand the fear — but more retries usually makes “pending” last longer because the system adds cooldowns.

“High risk” can mean the system saw unusual sign-in signals, not proof of a hacker. The safest thing is controlled checks and good notes.

Safe checklist (no risky steps):
• Look for a recent-security-activity page inside the account (it may show unfamiliar sign-ins).
• Make sure your recovery email/phone still works (so you can receive prompts).
• Stop repeated code requests and wait through any “try again later” message.

Trust moment: I don’t want you to click random “approve” prompts. Only approve a sign-in you started yourself.
Customer
I did see a couple of sign-in alerts that weren’t mine a few days ago. My grandson changed the password after that. Since then it’s been weird. Now it’s pending.
Technician avatar Technician
That sequence often triggers extra security: suspected access → password change → new 2FA → the system watches closely for a while.

At this point, “verification pending” may be a security hold or risk review — the system is waiting to see a stable, trusted sign-in attempt.

Safe tests that can identify the trigger without escalating the risk flag:
1) Trusted device test: try from the device you’ve used for months (if possible). New devices raise risk.
2) Network consistency: one attempt on home Wi-Fi only, then stop (don’t bounce between networks).
3) Browser clean test: a clean browser profile can reduce cookie/session conflicts, especially with strict tracking protection.
Customer
If it’s a security hold, how long does it last? And is it my computer settings or something broken?
Technician avatar Technician
It’s usually not “broken hardware.” It’s more often a security setting, risk score, or cooldown behavior.

The time can vary by provider and by how many attempts were made. That’s why the safest move is fewer retries and a stable environment.

What you can do right now that helps most seniors:
• Set phone time/date to automatic (for authenticator reliability).
• Use one trusted device for one attempt, then pause.
• Avoid VPN/proxy and avoid switching devices mid-flow.

If the provider offers “use another method,” choose the method you can reliably access (recovery email/phone), and don’t request codes repeatedly.
Customer
Okay. I’ll use only my phone for the next attempt and make sure the time is automatic. I’ll stop trying repeatedly. I just want a safe plan.
Technician avatar Technician
That’s a safe plan.

Final safety reminder: if anyone calls or messages asking for your verification code, password, or a “support PIN,” don’t share it. Real verification happens only inside the sign-in pages you opened yourself.

If the status changes (pending → approved, or pending → additional verification needed), write down the exact wording and time. That helps you and support understand whether the risk flag is de-escalating.

Quick answer: the accepted fix

Accepted safe steps when verification is pending due to a high risk flag:

• Stop rapid retries and wait through any cooldown (“try again later” can extend if you keep trying).
• Stabilize the sign-in: one trusted device, one browser/app, same home Wi-Fi, no VPN/proxy.
• Confirm 2FA reliability: phone time/date on automatic; use the recovery method you can access consistently.
• Check for security notices (recent activity alerts, “unusual sign-in,” or “additional verification needed”) and record exact wording/timestamps.


Why “High Risk Flag” can keep verification pending

A high-risk flag is usually part of risk-based authentication. The system looks at signals like new device, new browser, unusual location, IP address changes, VPN/proxy use, and how many sign-in attempts happened. If several signals appear at once (for example: password change + new authenticator + many retries), the system may hold verification in a pending state until it sees a stable, trusted attempt or until a cooldown ends.

What to check first (senior-friendly, no risky steps)

Use a calm checklist: pick one device (preferably the one you’ve used for months), keep the same network (home Wi-Fi), and avoid VPN/proxy. Check that your phone’s time is automatic so authenticator prompts work correctly. Look for in-app security messages or recent activity alerts, and write down the exact wording. Avoid requesting new codes repeatedly — it can trigger rate limits and keep verification pending.

Security tip: approve only sign-ins you started

High-risk flags often come after suspicious prompts.

If you receive a push approval or code request you did not start, do not approve it. Don’t share codes, passwords, or “support PINs” with anyone. Use only the provider’s sign-in screen you opened yourself. This keeps your account safe while the risk flag is active.

Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by device, region, and service. For exact instructions for your setup, consult a verified expert or the manufacturer’s support site.

Understand what these prompts mean


Getting Started Is Easy

Low-risk stability checks

Use one trusted device, one network, and one sign-in attempt to reduce risk signals and avoid cooldowns.

Keep 2FA reliable

Simple checks for authenticator time sync and consistent recovery methods, without changing security settings.

Escalation-ready notes

Record the exact “high risk” wording, timestamps, and what changed (password, device, travel) for faster triage.

FAQ

Why did verification become pending suddenly with a “High Risk Flag”?

This often happens after a change that looks unusual to the system, like a new device, location/IP change, VPN/proxy use, or many sign-in attempts. It can also happen after a password reset or adding a new authenticator app. The system may place a temporary hold while it confirms you are the real owner. Staying calm and avoiding repeated retries helps the flag clear faster.

Can this start after an update (phone or computer)?

Yes. Updates can change browser privacy rules, cookies, permissions, or how an authenticator app works. If the phone’s clock shifts, codes may not match, which can increase security friction. Avoid switching devices repeatedly during the flow. Use one device and make sure time/date is automatic.

Is this a hardware issue or a settings/security issue?

Most of the time it’s not hardware. It’s usually a security/risk score issue, a cooldown, or inconsistent sign-in signals (switching devices, VPN, many retries). Settings like strict tracking protection can interfere with sign-in cookies and keep verification pending. A stable device and network are the safest first test.

Can this be fixed without going to a service center?

Usually, yes. Seniors can often resolve it by waiting out cooldowns, using one trusted device, keeping the same network, and ensuring the authenticator phone time is correct. You don’t need a repair shop for a risk flag. If the provider requests additional verification, follow that prompt only inside the account’s real sign-in pages. If it stays pending unusually long, your notes help support investigate safely.

Sources

Filed under: Account Access Help

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant