Langflow Community Reports Missing PGVector Connection Parameters in Shareable Playground, Potentially Breaking Agent Retrieval

The Langflow community filed an issue on October 18 reporting that the official PGVector component works in the regular Playground, but vector retrieval can fail when the same flow runs through the Shareable Playground. This happens even though the agent has supplied search text: the connection parameters are empty. The reported environment uses a Docker deployment with Langflow and LFX 1.12.6, and lfx-bundles[pgvector] 1.1.38; this report does not establish that other versions are affected. Issue report

The error occurs while converting the connection string: the code receives an empty pg_server_url, then raises an exception because NoneType has no rsplit method. The reporter’s diagnostic logs indicate that the parameter was already missing before tool creation and deep copying, despite a valid connection environment variable being set inside the container. These clues point to parameter passing when the tool is created for a shareable flow, but the upstream cause has not been confirmed. Diagnostic logs

The official documentation defines pg_server_url as a secret string input, separate from the search_query supplied by the agent. The PGVector component then reads and writes to PostgreSQL through a LangChain vector store instance. For RAG flows using this architecture, a model’s successful tool selection and generation of a correct query do not by themselves show that the retrieval chain is working; runtime connection settings must also be verified. PGVector component documentation

The reporter temporarily configured the component to read PGVECTOR_CONNECTION_STRING when the value is empty, restoring retrieval and subsequent responses in the shareable flow. This is a local change, not an official fix. Deployment teams can use the report to plan side-by-side tests of the regular and shareable entry points, checking both the first and subsequent tool calls. Langflow states that the Shareable Playground is for testing only and that applications should use the API for integration. Follow-up questions include whether maintainers can reproduce the issue, how secret parameters are passed into the public execution path, and whether a fix will include regression tests. At the time of review, the issue remained open, with no linked fix proposal. Report and workaround, Playground usage guidance