Known limitations
A consolidated list of genuine, current limitations — not a change log, and not a list of resolved historical bugs. Each links to the page with full context.
Table of contents
Data API
- MySQL is the only supported engine for tenant data today. The architecture resolves its SQL dialect per request, so adding another engine doesn’t require restructuring — but none beyond MySQL is bundled yet. See Concepts → Architecture and Admin console → Engine roadmap.
- A background bulk-import job’s result isn’t persisted anywhere queryable. A queued import (row count over the realtime threshold) returns a
jobId, but there’s currently no endpoint to poll that job’s final outcome — you’d confirm completion by checking the data itself. See API reference → Bulk endpoints. - A multi-statement script is not wrapped in one transaction. If a script fails partway through, earlier statements stay applied. See API reference → Database & schema endpoints.
- Bulk import’s Google Drive source is stored but not yet read. The credential fields exist in Host Settings, ready for when this ships. See Admin console → Settings → Host Settings.
Generate Config
- No built-in cost control. Each call is a real, metered AI request, and nothing today stops repeated or automated regeneration from running up real cost. See Features → Generate Config & dashboards.
- GitHub is the only publishing backend, with no fallback — if your GitHub integration is unreachable, publishing fails even though the config itself still generates successfully. See Admin console → Settings → GitHub.
- Generated
accessRolesare placeholders ("root"), not your platform’s real role names. A frontend that compares a signed-in person’s actual role against these fields won’t get a meaningful result yet. See Features → Generate Config & dashboards. - A saved GitHub token or AI key needs a restart to take effect. Changing either in Host Settings updates what’s stored, but the running process keeps using the value it loaded at boot until restarted. See Admin console → Settings → Host Settings.
LoginLink
- “Check it still works” can report “no credential stored” even when one is. It also requires a LoginLink app object to exist, and conflates that separate missing-prerequisite into the same message. See Features → LoginLink integration.
Platform / operations
- No automated test suite for this repository’s own code. The private packages this platform depends on each carry substantial test suites in their own repositories; this repo’s own thin-host code (local controllers, builders, bridge classes) currently has none. See Deployment → CI/CD.
- Reverse-proxy trust defaults to “trust anything” if left unconfigured. Set
ReverseProxy__TrustedProxyIPsexplicitly in every real deployment — see Deployment → Environment variables.