In the middle of an AI session, Wappler turned black. Minimizing/maximizing Wappler didn't help refresh. Used Task Manager to force quit Wappler. This has happened before, but this time I am getting 500 Internal Server Error in the AI Manager. Error message persists after restarting laptop/Wappler.
If you are using the free tier of Copilot you may have consumed your quota. You can check your usage on the GitHub Copilot billing page (to ascertain if quota is indeed the issue):
I have remaining 150 premium requests. Maybe the last session got stuck, but it has been several hours since.
Depending on the size of the request you may be exceeding your quota or may have hit a rate limit. Really difficult to tell as the response from Copilot is not very informative as just throws a standard error. Don't think this is related to Wappler though. Think it is much more likely to be as a result of Copilot enforcing limits on the request. I could be wrong though.
I have the same problem with Copilot and for me it seems like a bug of the Wappler AI Manager since one of the last two release updates of Wappler (I use v7.3.8 at the moment).
I made several attempts, including very easy prompts for testing only (e.g. âadd one menu point âtestâ to the menu barâ) and changing the AI models and releases. The related .ejs file is only 250 lines at the moment and I have a Copilot Pro subscription with more than 200 premium requests left for this month.
When I switch to the chat provider OpenAI (where I also have a subscription) it doesnât work, too. With the same small file and the same easy test prompt I get the following error:
429 Request too large for gpt-4.1 in organization org-xxx on tokens per min (TPM): Limit 30000, Requested 88594. The input or output tokens must be reduced in order to run successfully. Visit https://platform.openai.com/account/rate-limits to learn more.
Two weeks ago there were no problems like this.
Fixed in Wappler 7.3.9
1 Like