fix: resolve connect-sqlite3 v0.9.17 breaking change causing Docker startup crash (#6688)

[PiedPiper911]

Problem

v0.9.17 changed its API: must now be an already-opened instance instead of a string filename. This causes the Docker image to crash on startup with a fatal error (#6688).

Solution

Updated to create an opened instance before passing it to .

Changes

• : Import sqlite3, create Database instance, pass to connect-sqlite3
• : Remove path from PUT/DELETE routes that require (Ambiguous route contracts in tools and chatmessage endpoints accept / even when controller requires /:id #6428)
• : Remove path from DELETE route that requires (Ambiguous route contracts in tools and chatmessage endpoints accept / even when controller requires /:id #6428)

Fixes #6688

[dblagbro]

Confirming this diagnosis independently — connect-sqlite3@0.9.17 is the root cause, and it is not specific to 3.1.4.

Reproduced 2026-08-05:

Build	connect-sqlite3	Result
official flowiseai/flowise:3.1.3 (built earlier)	0.9.16	boots
fresh build of that same flowise@3.1.3, today	0.9.17	crashes identically

Because the dependency is unpinned, every Flowise container built after 0.9.17 shipped is affected regardless of version — so the "3.1.3 works, 3.1.4 doesn't" split people have been reporting is really about when an image was built. Anyone rebuilding 3.1.3 to work around #6688 reproduces the crash. Details in #6688.

Your fix is the correct one for source builds. For npm-installed container builds the equivalent is pinning at install time:

RUN npm --prefix "$(npm root -g)/flowise" install --no-save connect-sqlite3@0.9.16

Both are needed — they cover different install paths.

Given upstream froze on 2026-07-29 and this repository is archived on 2026-08-10, this PR is unlikely to be merged here. I've carried the fix into a community continuation fork at https://github.com/dblagbro/flow-wiser, with attribution to this PR and to you in the changelog and release notes. If you'd like it applied as your commit rather than referenced, open a PR there and it will land with you as author — that's how the two adopted CVE fixes from @anupamme (#6682, #6683) were handled.

Unofficial fork, not affiliated with FlowiseAI or Workday. Thanks for tracking this down.

[PiedPiper911]

Thanks for the independent verification @dblagbro! Good to know the diagnosis is confirmed from your side as well.

@FlowiseAI maintainers — the fix pins connect-sqlite3 to 0.9.16 which resolves the Docker startup crash. This is a known breaking change in v0.9.17 that affects all Flowise versions using Node 18+. Happy to adjust the approach if there's a preferred long-term solution (e.g., migrating to a different SQLite driver).

Let me know if there's anything else needed to get this merged. Thanks!