# Resolved: Builds Failing Due to Page and/or Tag Too Long

**Update (Feb 8, 2023)**

Part of this issue has been resolved as part of [Release 74](https://docs.limio.com/release-notes/limio-commerce-release-notes/legacy-releases/limio-release-notes-release-740). In Release 74+, a manual build will no longer fail due to Page name, or Page tag length. However, using the mass build feature will still cause these long pages to fail the build. Please continue to use the workaround listed below in order to use the mass build feature.

**Issue:** Builds or bulk builds will fail if the Page name and Tag of the Page are too long. Limio uses a concatenation of both for its build. The character limit for the Page Name and Tag Name is currently is at 145 characters. This is a limit set by Limio infrastructure provider.

For example, SP The Betterley Report - Intellectual Property and Media Liability and /sp-betterley-report-intellectual-property-and-media-liability will be concatenated as 'sp-20-the-20-betterley-20-report-20-20-intellectual-20-property-20-and-20-media-20-liability-sp-20-the-20-betterley-20-report-20-20-intellectual-20-property-20-and-20-media-20-liability' (185 characters). This will cause Builds to fail. Note that Spaces are currently encoded as "-20-".

**Workaround:** Shorten the page name, the tag URL, or both to meet the 145 characters limit.

**Long-term fix:** This bug will be prioritised for our roadmap. This article will be updated as more information is available.


---

# Agent Instructions: 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:

```
GET https://docs.limio.com/support/known-issues/resolved-issue-builds-failing-due-to-page-andor-tag-too-long.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.