I’m not able to see any workflows in the web-ui after enabling advanced visibility. I wanted to know if this is something expected and if I need to somehow export & import my current running/failed/completed/… workflows after enabling advanced visibility?
Thanks for your reply but I’m pretty sure that I have created the index and template using the instructions here.
Also since I deploy using helm charts, initContainers wouldn’t start if the index has not been created.
pulls from your primary persistence store you configure in server static config
tctl wf l
pulls directly from your visibility store that you configure.
Seems there might be some issue with configuration/permissions defined.
You say that history service is able to move visibility tasks to ES (if you see data in ES) but frontend service is not able to poll it.
Could you check your server logs (frontend and history service) and also ES logs to see if there is anything that stands out?
Hi, we have a similar problem, although we don’t see any workflows in tctl neither web ui, not even new ones. Elastic seems to have the data and tctl describe also seems to work.
We had upgraded from older temporal and added advanced visibility.
BTW is elastic connection via TLS with authentication supported?
So for those who are curious, what I did, in the end, was to select workflow_id from public.executions_visibility where status=1; and then tctl reset-batch them. They showed up in UI and advanced visibility es afterwards