Skip to content

Known issues

OpenQuok limitations and environment pitfalls we track, with workarounds where they exist.

2 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start for $0

Known issues

Confirmed behavior that may look like a bug, plus workarounds when we have one.

We remove entries when a fix ships. If something is missing, report it on GitHub or Discord.

Channel connect

Invalid state on self-host with more than one API instance

OAuth state lives in cache for about one hour. If production uses in-memory cache across multiple API replicas, connect can fail with Invalid state even when you follow the flow correctly.

Workaround: use Redis for CACHE_PROVIDEROAuth and channel connect and Redis cache.

Uploads

Dashboard upload may not cancel cleanly

Closing the dialog or navigating away during an active upload can leave a partial upload running. The library may show the file only after the transfer finishes.

Workaround: wait for completion, then delete the asset from the library or post if you did not want it. Multipart API uploads can call abort-multipartAbort multipart.

Public API

Large JSON post bodies

Default JSON body size is about 10 MB. Inlining big base64 blobs in create-post requests triggers payload errors.

Workaround: upload media first, then reference id and pathUploads and media.

Where to report new bugs

ChannelBest for
GitHub issuesReproducible defects with version and steps
DiscordQuick questions, screenshots, self-host setup
[email protected]Cloud billing and account-specific problems
Search documentation
Find a docs page
Discord Support