cadence-workflowuber-cadence

How to detect if an older Cadence version is still running in Production and safe to delete?


What is the best mechanism to detect if an older Cadence version branch is still running in Production and safe to delete? It seems like Cadence’s logger is idempotent and won’t log > 1 time, so there is no way to tell from logs/data that a workflow’s version codepath is safe to remove.


Solution

  • Thanks for the question!

    We don't have a support for this right now but I created tasks to support following 3 metrics:

    Hopefully soon, we will support this