# Forge forge deploy fails at "Release CaaS manifest" with 500 — is there a limit on jira:jqlFunction modules?

**URL:** <https://community.developer.atlassian.com/t/forge-forge-deploy-fails-at-release-caas-manifest-with-500-is-there-a-limit-on-jira-jqlfunction-modules/99607>\
**Category:** Jira Cloud\
**Tags:** forge-deploy, jql, jira-cloud, forge\
**Created:** [March 14, 2026, 2:13am UTC](https://community.developer.atlassian.com/t/forge-forge-deploy-fails-at-release-caas-manifest-with-500-is-there-a-limit-on-jira-jqlfunction-modules/99607 "2026-03-14T02:13:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![JelsinStibenSanchezA](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/jelsinstibensancheza/32/55523_2.png) [@JelsinStibenSanchezA](https://community.developer.atlassian.com/u/JelsinStibenSanchezA)\
**Post date:** [March 14, 2026, 2:13am UTC](https://community.developer.atlassian.com/t/forge-forge-deploy-fails-at-release-caas-manifest-with-500-is-there-a-limit-on-jira-jqlfunction-modules/99607/1 "2026-03-14T02:13:51Z")

</div>

Hi everyone,

I’m building a Forge app that adds custom JQL functions to Jira Cloud using the `jira:jqlFunction` module type. My app currently registers 57 JQL functions, and I’m working toward a total of 111.

Recently, forge deploy started failing at the “Release CaaS manifest” step with the following error:

`App environment update failed`  
`Validation errors: {`  
`“extensions”: {`  
`“errorType”: “INTERNAL_SERVER_ERROR”,`  
`“statusCode”: 500`  
`}`  
`}`

Importantly, the deployment succeeds through all earlier steps — manifest validation passes, Lambda functions are released — and only fails at this final CaaS manifest registration step.

So my question is, why do I get his problem? I something from attlasian server? or Is there a hard on how many jira:jqlFunction modules a single Forge app can register? maybe that is the error, I would like find a solution. Thanks