How to avoid a error notfication (error 400) in purview

Question

How to avoid a error notfication (error 400) in purview

KASICA, Francis 5

I add as children more than 2000 glossaryterms to a glossary. And after that, I get a error notification when I display this glossary when I open this in microsoft purview website

Request failed with status code 400
Request ID: a1a1a1a1-bb3b-3333-c3f6-7s7k9l38ed8
The query request is invalid. Please check the payload and try again.

I happens when I try to open the glossary

norman Gallynhaal 0 Reputation points

2026-06-24T10:16:18.7566667+00:00

I’ve run into similar issues when working with very large glossaries in Purview. Once you start adding thousands of child terms, the payload size can exceed what the service expects, which often triggers the 400 invalid request error you’re seeing.

A few things that can help:

Try breaking the glossary into smaller sub‑glossaries or categories instead of one massive parent.

Use the Purview REST API or bulk import tools — they handle large datasets more reliably than the UI.

Clear browser cache and re‑authenticate; sometimes stale sessions cause false “file in use” errors.

If the error persists, raise a support ticket with the Request ID included — Microsoft can trace the failing query.

3 answers

Your answer

norman Gallynhaal 0 Reputation points

2026-06-24T10:16:18.7566667+00:00

I’ve run into similar issues when working with very large glossaries in Purview. Once you start adding thousands of child terms, the payload size can exceed what the service expects, which often triggers the 400 invalid request error you’re seeing.

A few things that can help:

Try breaking the glossary into smaller sub‑glossaries or categories instead of one massive parent.

Use the Purview REST API or bulk import tools — they handle large datasets more reliably than the UI.

Clear browser cache and re‑authenticate; sometimes stale sessions cause false “file in use” errors.

If the error persists, raise a support ticket with the Request ID included — Microsoft can trace the failing query.

Answer 1

KASICA, Francis 5

Hello,

I build a script to read all glossaryterms under a specific glossary though the REST API, it runs without errors even if I get all glossaryterms. But a notification error occurs when I display the children of this glossary in the purview site. This only happens in this case.

0 comments

Answer 2

Pilladi Padma Sai Manisha 10,770 Microsoft External Staff Moderator

Hi @KASICA, Francis
Based on the information provided, there is no documented Microsoft limit indicating that adding more than 2,000 child glossary terms should result in a 400 error when opening a glossary.

To help narrow down the issue, could you please confirm:

Were the glossary terms added through the Purview portal, REST API, or bulk import?
Does the issue occur in multiple browsers or an InPrivate/Incognito session?
Approximately how many child terms were added when the issue first occurred?

If possible, also verify whether the glossary can be retrieved successfully using the Purview REST APIs. If the APIs work but the portal fails, it would help determine whether the issue is specific to the portal.

KASICA, Francis 5 Reputation points

2026-06-29T09:02:04.74+00:00

the glossary terms were added by bulk import. I don't know at what point the problem appeared. I happens only in the microsoft purview administration site.
Pilladi Padma Sai Manisha 10,770 Reputation points Microsoft External Staff Moderator

2026-06-29T10:46:22.0766667+00:00
Thank you for the additional information.

Since the glossary terms were added through bulk import and the issue occurs only in the Microsoft Purview portal, it suggests the glossary data was imported successfully, but the portal is encountering an issue when loading or rendering the glossary.

To help investigate further, could you please confirm:

Does the glossary remain accessible through the Purview REST APIs, or does the error occur there as well?

Approximately how many glossary terms were imported in total?
KASICA, Francis 5 Reputation points

2026-06-29T14:07:46.42+00:00

Hello,
There was no error when I added all glossary terms to this specific glossary. The number of glossary terms imported was about 2750 elements.
Pilladi Padma Sai Manisha 10,770 Reputation points Microsoft External Staff Moderator

2026-07-01T02:16:30.83+00:00

Thank you for the update.

Since the bulk import completed successfully and the issue only occurs when opening the glossary in the Microsoft Purview portal, while the glossary contains approximately 2,750 terms, this does not appear to indicate a documented product limit. Instead, it suggests the issue may be related to how the portal is processing or rendering a glossary of this size.

As a next step, could you please check whether you're able to retrieve the glossary by using the Purview REST API? If the API returns the glossary successfully while the portal continues to return the 400 error, it would help confirm that the issue is specific to the portal experience.

If possible, please also let us know whether the error occurs only when opening this particular glossary or if other glossaries in the same Purview account can be opened without issue. That comparison will help further narrow down the scope of the problem.

Answer 3

KASICA, Francis 5

this problem occurs not in a api but in the webpage of microsoft purview. I can't change anything of that

0 comments