Langfuse integration not persisting after Open WebUI container restart

[m0hssn]

Problem Statement:
I'm using OpenWebUI with the Pipelines feature to send traces to Langfuse. I have configured persistent Langfuse public key (pk) and secret key (sk) as environment variables in my Docker Compose file and passed them to the OpenWebUI Pipelines container.
When I start the containers, everything loads successfully. I can see the pk and sk are set correctly when I navigate to the OpenWebUI Pipelines tab in the UI. However, when I send chat messages, no data is transmitted to Langfuse.
The only way to get it working is to manually navigate to the Pipelines configuration page in the OpenWebUI interface and click the "Save" button without changing anything. After doing this, the Langfuse integration starts working and traces are sent properly.
The Core Issue:
After every Docker container restart, I have to repeat this manual "Save" action for the pipeline to become active and start sending data to Langfuse. The environment variables are present and visible in the UI, but the pipeline doesn't actually initialize or function until I explicitly save the configuration through the UI.
What I Need:
A way to automatically activate/initialize the Langfuse pipeline on container startup so that it works immediately without requiring manual intervention through the UI after each restart. The pipeline should read the environment variables and become fully operational without needing the manual save action.
Pipeline in use:
https://github.com/open-webui/pipelines/blob/main/examples/filters/langfuse_v3_filter_pipeline.py

[m0hssn]

I found out that you can set the SK and PK directly in the Langfuse Docker Compose file and also in the OpenWebUI pipelines container, so they’re automatically applied on startup. You can then run the following command inside the OpenWebUI pipelines container to set the pipeline settings:

curl -s -X POST http://localhost:9099/pipelines/reload \
  -H "Authorization: Bearer $API_KEY"

If you add this command to a small bash script in the Docker Compose setup, it will run automatically when the service starts.