Server not responding Unable to access regulatory documents right now. Please try again later.

Question

Server not responding Unable to access regulatory documents right now. Please try again later.

ERIC PROSHUTO 0

I am attempting to update regulatory documents for SMS messaging, receiving this error constantly: Server not responding Unable to access regulatory documents right now. Please try again later.

Aditya N 2,990 Reputation points Microsoft External Staff Moderator

2026-06-16T18:01:52.4166667+00:00

Hello @ERIC PROSHUTO Thank you for reaching out Microsoft Q&A. Could you please let us know how long are you facing this issue?

Please could you confirm if you tried refreshing and trying again. Clearing cache or using another browser?
ERIC PROSHUTO 0 Reputation points

2026-06-16T19:12:32.72+00:00

I have cleared the browser cache, I have used incognito, tried several browsers. the issue is ongoing.
ERIC PROSHUTO 0 Reputation points

2026-06-16T19:37:28.03+00:00

this issue is in your form.
please review
developer tools in the browser shows this error:

Request Method

POST

Status Code

400 Bad Request

Remote Address

150.171.109.183:443

Referrer Policy

strict-origin-when-cross-origin
ERIC PROSHUTO 0 Reputation points

2026-06-17T14:32:47.78+00:00

Toll-free verification update application returns 400 Bad Request on submit. Application ID: 3db56750-95ea-408f-acba-23567787d381. Portal error: "Server not responding." Need manual resubmission with updated business email ******@landforge.us per rejection reason from May 22 2026.

2 answers

Your answer

Aditya N 2,990 Reputation points Microsoft External Staff Moderator

2026-06-16T18:01:52.4166667+00:00

Hello @ERIC PROSHUTO Thank you for reaching out Microsoft Q&A. Could you please let us know how long are you facing this issue?

Please could you confirm if you tried refreshing and trying again. Clearing cache or using another browser?
ERIC PROSHUTO 0 Reputation points

2026-06-16T19:12:32.72+00:00

I have cleared the browser cache, I have used incognito, tried several browsers. the issue is ongoing.
ERIC PROSHUTO 0 Reputation points

2026-06-16T19:37:28.03+00:00

this issue is in your form.
please review
developer tools in the browser shows this error:

Request Method

POST

Status Code

400 Bad Request

Remote Address

150.171.109.183:443

Referrer Policy

strict-origin-when-cross-origin
ERIC PROSHUTO 0 Reputation points

2026-06-17T14:32:47.78+00:00

Toll-free verification update application returns 400 Bad Request on submit. Application ID: 3db56750-95ea-408f-acba-23567787d381. Portal error: "Server not responding." Need manual resubmission with updated business email ******@landforge.us per rejection reason from May 22 2026.

Answer 1

ERIC PROSHUTO 0

400 again and now also a 404 on $value. The portal is definitively broken on your end — this isn't my data, my browser, or my submission. Microsoft's TFV submission API is returning errors.

Network diagnostics tab shows the submit call returning 400 AND a $value call returning 404. That 404 is likely the portal trying to fetch something that doesn't exist in your backend — a Microsoft-side bug.

0 comments

Answer 2

Mehmood Ali 0

Hi @ERIC PROSHUTO ,

Thanks for reporting this. The error you're seeing:

"Server not responding - Unable to access regulatory documents right now. Please try again later."

typically points to a temporary issue reaching the regulatory documents service, rather than a problem with your account or your documents. In most cases it clears on its own, but please try the following so we can rule out the common causes:

Refresh your session: log out fully, then log back in. An expired session often shows up as this exact error.
Try a different browser or an incognito/private window: this clears any cached data that may be interfering.
Turn off any VPN, proxy, or ad-blocker while updating, as these can block the document service.
Wait a few minutes and retry: if it's a brief server-side hiccup, a short wait usually resolves it.

ERIC PROSHUTO 0 Reputation points

2026-06-17T14:33:35.91+00:00

verification update application returns 400 Bad Request on submit. Application ID: 3db56750-95ea-408f-acba-23567787d381. Portal error: "Server not responding." Need manual resubmission with updated business email ******@landforge.us per rejection reason from May 22 2026.
ERIC PROSHUTO 0 Reputation points

2026-06-17T14:35:16.8866667+00:00

this is a bug and it needs fixed. in the mean time I am dead in the water.
ERIC PROSHUTO 0 Reputation points

2026-06-17T14:37:28.2533333+00:00

400 again and now also a 404 on $value. The portal is definitively broken on your end — this isn't my data, my browser, or my submission. Microsoft's TFV submission API is returning errors.

Network diagnostics tab you shows the submit call returning 400 AND a $value call returning 404. That 404 is likely the portal trying to fetch something that doesn't exist in your backend — a Microsoft-side bug.