-
Hello, We recently updated Conductor to the latest build from the main branch, and have run into an issue with deployment in one of our test environments: paste of server logs: the key part here is: this is a fresh install of conductor, with branch new containers and the only workflows that even should exist are the kitchensink samples How can I get Conductor to ignore this ghost workflow? I am fine with losing data, this is all during development so I am not worried about that edit: ["a42e81c4-07e2-4c20-b8a7-837f6a2af9e8","7bdd9c01-e9cd-4a84-a78d-98a73aa252c6"] running curl /api/workflow/search returns: {"totalHits":2744,"results":[]} I think this might be why the UI shows no results, but why would the workflow search be empty? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Well, I solved this issue by deleting all the indices in elastic and restarting conductor-server. For some reason, I had to do this twice before it worked, but it eventually did work |
Beta Was this translation helpful? Give feedback.
Well, I solved this issue by deleting all the indices in elastic and restarting conductor-server. For some reason, I had to do this twice before it worked, but it eventually did work