---
title: "Troubleshooting API category and navigation issues"
slug: "troubleshooting-api-category-and-navigation-issues"
updated: 2026-07-27T04:32:43Z
published: 2026-07-27T04:32:43Z
canonical: "docs.document360.com/troubleshooting-api-category-and-navigation-issues"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.document360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting API category and navigation issues

### Nested categories not displaying correctly
 
**When it occurs:** Endpoints that should appear in nested subcategories are not organised hierarchically after import.
 
**How it works:** Document360 supports second-level subcategories using the `>` symbol in OpenAPI tags. For example, a tag of `Pets > Details` will create a `Pets` category with a `Details` subcategory inside it. This structure is preserved during resync operations.
 
```yaml
tags:
  - name: "Pets > Details"
```
 
> ℹ️ **NOTE**
> The API documentation workspace supports a maximum of three levels of subcategories. If your spec includes more than three levels, any additional levels are placed at the third level.
 
---
 
### Category order is not what I expected
 
**When it occurs:** After uploading a spec, categories appear in a different order than expected.
 
**Why it happens:** Categories in Document360 are created based on the tag order defined in the spec file. The order of tags in your spec determines the order categories appear in the documentation.
 
**How to fix it:** Reorder the `tags` array in your OpenAPI spec to match the desired category order, then resync.