> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/fix/snyk-pull-or-merge-requests/customize-pr-templates/troubleshooting-and-limitations-for-custom-pr-templates.md). # Troubleshooting and limitations for custom PR templates Troubleshooting and limitations for Snyk custom PR templates ## Troubleshooting custom PR templates If you encounter an error, check your template and follow these instructions. ### Check template syntax Ensure that the template is written in valid `JSON` syntax for API and `mustache` syntax for the YAML file. Any syntax errors can lead to unexpected behavior. Check the syntax and make any necessary changes. ### Verify variable names Review the variables used in the template and ensure they match the supported variables in the [Variables list and description](/scan-fix-and-prevent/fix/snyk-pull-or-merge-requests/customize-pr-templates/variables-list-and-description.md). If a variable is misspelled or not recognized, it may cause unexpected output or a fallback to default values. ### Combination of YAML and API template If you open a custom PR template with values from both the YAML upload template and the API template, this is the expected behavior. Refer to the [order of precedence for processing custom PRs](/scan-fix-and-prevent/fix/snyk-pull-or-merge-requests/customize-pr-templates.md). If you do not want to see this combination, depending on your preference, either remove the YAML template or delete your API template. ## Limitations of custom PR templates ### Jira tickets in your PR You can add Jira tickets to your PR, but Snyk is limited to those created using Snyk workflows, either UI or API. ### Failure to open PR If a PR cannot be opened, Snyk cannot identify errors when a PR cannot be opened. ### No line between variables When you are customizing the YAML file, it is possible that a new line will not be added between variables when two lines start with a variable `{{}}`. --- # 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.snyk.io/scan-fix-and-prevent/fix/snyk-pull-or-merge-requests/customize-pr-templates/troubleshooting-and-limitations-for-custom-pr-templates.md?ask=&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.