> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/support-resources/knowledge-base-articles/design-studio/test-case/pipe-character-not-allowed-in-reusable-test-step-group-names.md).

# Pipe Character Not Allowed in Reusable Test Step Group Names

**Summary**: When you rename a reusable test step group, Avo Assure rejects names that contain pipe character (|).&#x20;

### Error Behaviour&#x20;

When this issue occurs, you may observe the following behaviours:&#x20;

* When you rename a reusable test step group, Avo Assure rejects a name that contains the pipe character (|).&#x20;
* This validation may appear inconsistent with the validation that applies when you create or edit a regular test step group.&#x20;

### Possible Reasons&#x20;

This issue may occur due to one or more of the following reasons:&#x20;

* The reusable execution flow treats the pipe character (|) as a special character.&#x20;
* Regular test step groups that are not in the Reusable Library do not have this restriction.&#x20;

### Resolution/Solution&#x20;

To resolve this issue and ensure successful execution, perform the following actions:&#x20;

1. Use supported characters in reusable test step group names, such as alphanumeric characters, spaces, and underscores (\_).&#x20;
2. Do not use the pipe character (|) or other restricted special characters in test step groups that you plan to use as reusable test steps.&#x20;
3. If a reusable test step group name contains a restricted character, rename the group with supported characters before you use it for reusable execution.&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/support-resources/knowledge-base-articles/design-studio/test-case/pipe-character-not-allowed-in-reusable-test-step-group-names.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
