I noticed there’s a feature in the Temporal UI for importing Event History, but I have not been able to figure out how to use it. At first glance, it seems like I should be able to take my archived workflow execution JSON files and rehydrate them so I can see them in the UI but that doesn’t seem to work. The formats seems inconsistent.
Is there any documentation on how I could rehydrate archived workflow executions into the Temporal UI?
How are you getting the event history json for your archived executions, from web ui itself?
Can you try getting it via tctl or cli, for example:
tctl wf show -w <wfid> -r <runid> --of myhistory.json
and then try to import the contents of myhistory.json in web ui, let us know if this works better for you.
Hi @tihomir,
Thanks for this feature, we’ve been enjoying integrating Temporal into our systems.
Is there any way to send a POST request or similar in the UI server/UI with a history.json file, so it can be automated?
Our current planned plan is to be able to link our existing metadata system to temporal using WorkflowID/RunIDs, so I’d like to use the API to fetch the history events for a workflow, and upload the JSON to the temporal UI.
Unfortunately, this will require a manual step as the HistoryEvent parsing is performed in JS: https://github.com/temporalio/ui/blob/3a6465f95c4c346ea9831830003bb5d1247de238/src/lib/components/import/event-history-file-import.svelte#L25.
Note, some of these workflows are archived (and out of the DB retention for visibility), so I can’t simply use the main UI because describe (ui/api/v1/namespaces/X/workflows/Y/runs/Z) doesn’t work for archived.
Happy to open this as a ticket/feature.
