Technical Report – Issues with public Schema, Connection Pool Timeout, and Session/DataStore Disappearing in Wappler

Wappler General Bugs
, , , ,
1

Hello Wappler team,

We are experiencing three major issues while developing a highly customized app using Wappler with PostgreSQL, self-hosted infrastructure, and full code control.

1. public Schema Not Recognized

Wappler does not automatically recognize the public schema in SQL queries. Every time we use nomedocampo or meubanco, we get an error saying the relation does not exist — although it works perfectly fine using DBeaver or raw SQL.

We tried explicitly adding public.nomedocampo, but the behavior is still inconsistent and unreliable.

Real error:
{
"status": "500",
"code": "42P01",
"message": "select count() as "Total" from (select from "nomedocampo") as "t1" limit $1 - relation "nomedocampo" does not exist",
...
}

We found a similar issue reported earlier: :link: Error reading data in non public schemas in postgres
Apparently, this bug was fixed in version 4.7 but has returned in version 6.x.

2. Timeout Acquiring Database Connection

We also encountered this error while running basic tests. It seems the connection pool is either full or not properly managed:

Real error:
{
"status": "500",
"message": "Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?",
...
}

This occurs even under low load, suggesting a possible issue with connection release or pool misconfiguration.

3. Session/DataStore Fields Disappearing

A persistent and critical bug: Session and DataStore fields randomly disappear from the UI panel, even with properly configured App IDs. This happens across all projects — new and existing.
Open issue: Session and Datastore fields disappearing + ghost windows on startup

These issues are causing significant project delays, damaging client trust, and affecting personal productivity. We kindly request urgent investigation and, if possible, an official fix or temporary workaround.

Wappler Version: Beta 7.0.0-b23
Operating System: Windows 11

Thank you for your support.
Rafael – Pense Moderno

1 Like
2

I cant help with the issues, however, its not a wise move to use a beta version for any client facing production work. For production, you'd be better using version 6.8. stable until V7 stable is released..

3

Unfortunately, the same issues are persisting even in version 6.8. We created a brand new project from scratch to test it — no migrations, no external code — and the exact same problems happened again.

This confirms that the issues are not related to project configuration or legacy settings.

Could you please confirm if these bugs are being tracked internally and whether any hotfixes or workarounds are available in the meantime? We are willing to run additional tests or provide deeper logs if needed.

These bugs are blocking production deployment and affecting multiple clients relying on our Wappler-based solution.

We appreciate any updates and thank you for your continued support.

Best regards,
Rafael – Pense Moderno