> For the complete documentation index, see [llms.txt](https://docs.pynt.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pynt.io/documentation/api-security-testing/pynt-scans-troubleshooting/pynt-for-postman-troubleshooting/troubleshoot-non-unique-collection-name-error.md).

# Troubleshoot Non-Unique Collection Name Error

{% hint style="danger" %}
**At a Glance**: ⚠️ This error in Pynt occurs when there are duplicate collection names in Postman, causing conflicts during testing. Follow this guide to resolve the issue by ensuring each collection has a unique name.
{% endhint %}

***

## Error: More than one collection with the same name was found

### What Happened?

Your Postman workspace has multiple collections with the same name, making it unclear which one to use.

### How to Resolve?

1. **Make Collection Name Unique**: Rename the collection in Postman to ensure it's unique.
2. **Use Collection ID**: Alternatively, provide Pynt with the **collection ID** instead of the name. The collection ID can be found in the collection properties in Postman UI.

***

{% hint style="info" %}
For additional support, visit [Pynt Community Support](https://www.pynt.io/community).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pynt.io/documentation/api-security-testing/pynt-scans-troubleshooting/pynt-for-postman-troubleshooting/troubleshoot-non-unique-collection-name-error.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.