From 079aafd833541f02cba79408a831c7705e219174 Mon Sep 17 00:00:00 2001 From: Aowss Ibrahim Date: Mon, 4 Dec 2023 09:04:09 -0500 Subject: [PATCH] Add small clarification about retries in BPMN models --- docs/Camunda.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/Camunda.adoc b/docs/Camunda.adoc index 4d5827b..c25eece 100644 --- a/docs/Camunda.adoc +++ b/docs/Camunda.adoc @@ -78,7 +78,9 @@ It should therefore have no dependency on any Camunda classes. * Use the https://docs.camunda.io/docs/components/modeler/bpmn/error-events/[BPMN Error event] for business errors and https://docs.camunda.io/docs/components/concepts/incidents/[Camunda Incidents] for technical errors -In particular, use Camunda's built-in https://docs.camunda.io/docs/components/best-practices/development/dealing-with-problems-and-exceptions/#leveraging-retries[retry mechanism]. +Do not model the retries of service tasks into the BPMN model as mentioned in https://camunda.com/blog/2021/04/where-is-the-retry-in-bpmn-20/[Where is the “retry” in BPMN 2.0?]. + +Use Camunda's built-in https://docs.camunda.io/docs/components/best-practices/development/dealing-with-problems-and-exceptions/#leveraging-retries[retry mechanism]. * Follow Camunda's https://docs.camunda.io/docs/components/best-practices/modeling/naming-technically-relevant-ids/#using-naming-conventions-for-bpmn-ids[best practices] regarding ID names