From 154ca89fbf5065377e75988593c25706134b2182 Mon Sep 17 00:00:00 2001 From: Walter Medvedeo Date: Wed, 22 May 2024 08:59:05 +0200 Subject: [PATCH] Update serverlessworkflow/modules/ROOT/pages/persistence/core-concepts.adoc Co-authored-by: Kalyani Desai <43639538+kaldesai@users.noreply.github.com> --- .../modules/ROOT/pages/persistence/core-concepts.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverlessworkflow/modules/ROOT/pages/persistence/core-concepts.adoc b/serverlessworkflow/modules/ROOT/pages/persistence/core-concepts.adoc index 9d5079568..b20818d4b 100644 --- a/serverlessworkflow/modules/ROOT/pages/persistence/core-concepts.adoc +++ b/serverlessworkflow/modules/ROOT/pages/persistence/core-concepts.adoc @@ -14,7 +14,7 @@ Each mechanism is intended for different a purpose: image::persistence/Persistence-Types.png[] == Workflow runtime persistence -The workflow runtime persistence is designed to ensure that your workflow instances remain consistent in the context of an error or a runtime restart. For example, a pod restart, a programmed maintenance shutdown, etc. +The workflow runtime persistence ensures that your workflow instances remain consistent during an error or a runtime restart. For example, a pod restart, a programmed maintenance shutdown, etc. This is achieved by storing snapshots of the executing workflow instances [xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc#saving_of_workflow_snapshots[see more details]]. That information is stored in an internal format, and usually, you must only focus on providing the proper configurations to use it.