Skip to content

Shareable Playground resets input/fails to render response in v1.8 (Self-hosted with Postgres on NFS) #12283

@nstrande

Description

@nstrande

Bug Description

After updating to Langflow 1.8 (self-hosted), the Shareable Playground is non-functional, while the internal Playground works perfectly. When a prompt is sent in the Shared Playground, the chat input field resets/clears immediately, but no response is rendered, and no message appears in the chat history.

This issue persists despite trying both Global Variables (Credentials) and hardcoded local variables directly in the components. The environment uses PostgreSQL on an NFS mount, and custom component/config paths are defined.

Reproduction

Langflow Version: 1.8 (Self-hosted)

Database: PostgreSQL (Stored on NFS mount)

Deployment: Docker

Environment Variables:
LANGFLOW_AUTO_LOGIN=false
LANGFLOW_COMPONENTS_PATH=/app/custom_components
LANGFLOW_CONFIG_DIR=/app/langflow

Expected behavior

The Shareable Playground should function identically to the internal Playground.

Specifically:
Response Rendering: Upon sending a message, the Chat Output should display the response from the LLM in real-time (streaming) or as a completed message.
State Persistence: The message should appear in the chat history/bubbles within the UI instead of the input field simply resetting to an empty state.
Session Resilience: The shared session should be able to execute the flow even if non-critical services (like Openlayer tracing) are unconfigured or if there is minor latency in the backend database (PostgreSQL on NFS).
Credential Inheritance: The shared session should correctly inherit and utilize the provided credentials (either from Global Variables or hardcoded values) to authenticate with external providers (e.g., OpenAI/Azure OpenAI).

Who can help?

No response

Operating System

Ubuntu Linux 22.04

Langflow Version

1.8.1

Python Version

None

Screenshot

No response

Flow File

No response

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingjiraThis issue has been logged in Jira for fix by the engineering team.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions