Nek-11
Nek-11
**Describe the feature you'd like** Provide an official dockerfile.worker and a corresponding published Docker Hub image (e.g., flowiseai/flowise-worker) specifically for running Flowise workers. This would standardize and simplify deploying Flowise...
[BUG] BullMQ removeOnComplete/removeOnFail count setting not working properly for prediction queue
# BullMQ removeOnComplete/removeOnFail count setting not working properly for prediction queue ## Describe the bug **When running Flowise in queue mode with Redis, the `REMOVE_ON_COUNT` environment variable is not correctly...
**Describe the bug** When using the Postgres Record Manager node with an Azure PostgreSQL Flexible Server database, the updated_at column (double precision type) in the specified record manager table (e.g.,...
**Describe the bug** There's a bug in all the Retrievers that have a "Query" field, when being used as "Retriever" (as opposed to "Document" or "Text"). The Query clearly states:...
**Problem:** Running Flowise workers effectively in various environments, especially scaled deployments or platforms like Azure App Service, presents several challenges: 1. **Lack of Official Worker Dockerfile:** There is no official,...
**Problem:** The current `Conversational Retrieval Tool Agent` node (introduced in PR #2430 ) lacks two important capabilities: 1. When using follow-up questions, the node doesn't have the ability to rephrase...
Patch for #4377 This PR addresses an issue where Redis connections would unexpectedly close after periods of inactivity, particularly with @redis/client instances. The key changes: - Added both TCP-level keepAlive...
In #4381 I proposed a fix for time handling and schema creation in PostgresRecordManager. However, I made a mistake there. The `CREATE EXTENSION IF NOT EXISTS pgcrypto;` line causes failures...
Hey, First of all, great tool, thanks for creating it. I'm trying to export a table of the filtered view I created to be able to only extract a precise...