Not able to see the existing workflows after re installation of temporal setup in kubernets

Community Support Server Deployment
1

Hi, We have setup Temporal setup on GCP Kubernetes using Helm Chart. We are using Cloud SQL PostgreSQL to store the temporal Data. We had some running workflows in the temporal. Due to some issues, we deleted and reinstalled the Temporal server setup and connected back to the same old DB.

But even though we connected to the old DB instance and DB has all the current workflows in it, when we launched the Temporal UI, there are no workflow. It shows the namespace and no running workflows. In PostgreSQL DB we can see those workflows and but not in the Temporal UI.

Based on some investigation, we guess the issue could be with the Elastic search Indices, though not sure. If so, there is any way to restore or create the indices from the DB??

How to ensure that in the future we don’t lose such workflows in Temporal in case of re installation? What configuration we need to perform with Helm chart setup to preserve the data.

Support is greatly appreciated.

2

when we launched the Temporal UI, there are no workflow
we guess the issue could be with the Elastic search Indices

yes that is most likely issue. ui uses visibility api and data from your visibility store to list executions

there is any way to restore or create the indices from the DB??

unfortunately no. if you reindex ES or restart es and re-build indices only way would be to manually insert this data which is not easy to do

How to ensure that in the future we don’t lose such workflows

typically you would set up your db and ES indexes manually and not do it automatically by disabling db create: helm-charts/charts/temporal/templates/server-job.yaml at main · temporalio/helm-charts · GitHub

3

Thanks for the details, we skipped Elastic search and used Postgresql for visibility. As the number of workflows are less in our application, we decided to go with Postgresql.