Currently, archived workflows remain in the search index (if using ElasticSearch) without removal, and archiving does not work without Redis. There are no per-workflow archiving settings. A possible workaround involves manual removal from the index or moving data to S3.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
How does conductor keep the outputs of task, especially when the task in a workflow is completed? | 0 | 9 | January 2, 2025 | |
How to configure workflow data persistence in Conductor with PostgreSQL? | 0 | 5 | January 22, 2025 | |
How to optimize Conductor performance for large traffic? | 0 | 11 | January 22, 2025 | |
Configuring Redis properly for Conductor | 0 | 7 | January 22, 2025 | |
Why is a completed workflow still in the running state? | 0 | 6 | January 22, 2025 |