Maybe you can start with looking at the sample for solving the same "subscription" use case: Temporal: https://github.com/temporalio/subscription-workflow-pro

Maybe you can start with looking at the sample for solving the same "subscription" use case: Temporal: https://github.com/temporalio/subscription-workflow-project-template-go https://github.com/temporalio/subscription-workflow-project-... https://github.com/temporalio/subscription-workflow-project-template-java https://github.com/temporalio/subscription-workflow-project-... iWF: https://github.com/indeedeng/iwf-java-samples#product-use-case-samples https://github.com/indeedeng/iwf-java-samples#product-use-ca... https://github.com/indeedeng/iwf-golang-samples#product-use-case-samples https://github.com/indeedeng/iwf-golang-samples#product-use-... Note that you need to consider making changes to workflow -- in Cadence/Temporal, you must use versioning like: https://stackoverflow.com/questions/61298415/how-can-i-version-cadence-workflows https://stackoverflow.com/questions/61298415/how-can-i-versi... And this versioning/determinism constraints is just a small part of the learning curves for complicated project And I am not the only one pointing this out. Also see the article from the principal of Azure Durable Function team: https://medium.com/@cgillum/common-pitfalls-with-durable-execution-frameworks-like-durable-functions-or-temporal-eaf635d4a8bb https://medium.com/@cgillum/common-pitfalls-with-durable-exe...