{"id":577,"date":"2026-02-25T10:20:37","date_gmt":"2026-02-25T10:20:37","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/"},"modified":"2026-02-25T10:20:37","modified_gmt":"2026-02-25T10:20:37","slug":"bpmn-boundary-event-mistakes","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/","title":{"rendered":"Event Sub-Processes and Boundary Events Used Incorrectly"},"content":{"rendered":"<p>Boundary events are powerful, but their misuse can introduce hidden logic that breaks process behavior. I&rsquo;ve seen teams deploy processes that fail silently because a boundary event was attached to the wrong task or triggered in an unintended context. The root issue? Confusion between interrupting and non-interrupting behavior, and failing to recognize when a simple exception flow would suffice.<\/p>\n<p>These errors aren&rsquo;t just cosmetic. A misapplied boundary event can prevent a process from completing, create parallel execution paths, or make error recovery impossible. This chapter cuts through the noise with real-world patterns, clarifying when to use boundary events, when to avoid them, and how to model exceptions properly.<\/p>\n<p>By the end, you\u2019ll be able to distinguish between a timeout, cancellation, and error condition \u2014 and model each with precision, clarity, and control.<\/p>\n<h2>When Boundary Events Are Misused<\/h2>\n<p>Boundary events are attached to a task or activity and trigger when a specific condition occurs. But their power comes with responsibility. They\u2019re often misused when modelers don\u2019t understand their <strong>execution context<\/strong>.<\/p>\n<p>One common error: attaching a boundary event to a task that\u2019s meant to be atomic. If a task like \u00ab\u00a0Process Payment\u00a0\u00bb is interrupted by a \u00ab\u00a0Timer\u00a0\u00bb boundary event, the system must re-execute the task or handle the interruption \u2014 but this breaks the atomic nature of the action.<\/p>\n<p>Another issue: using a boundary event to model an exception that should be handled via a standard error flow. This creates redundancy and increases complexity without benefit.<\/p>\n<h3>Common Pitfalls in Boundary Event Use<\/h3>\n<ul>\n<li>Using a <strong>timer boundary event<\/strong> on a task that\u2019s already governed by a time limit \u2014 leading to double triggers.<\/li>\n<li>Applying a <strong>cancel event<\/strong> to a task that\u2019s already in a subprocess \u2014 causing unintended termination.<\/li>\n<li>Attaching a <strong>error boundary event<\/strong> to a non-throwing task \u2014 resulting in no execution path.<\/li>\n<li>Using multiple boundary events on the same task without clear precedence \u2014 creating ambiguity.<\/li>\n<\/ul>\n<p>These mistakes stem from a lack of understanding about how boundary events interact with the parent activity\u2019s lifecycle. They\u2019re not event listeners \u2014 they are part of the execution flow.<\/p>\n<h2>Understanding the Two Types: Interrupting vs. Non-Interrupting<\/h2>\n<p>Boundary events come in two forms: interrupting and non-interrupting. Confusion here leads directly to behavioral errors.<\/p>\n<p>An <strong>interrupting boundary event<\/strong> stops the parent activity from completing. It&rsquo;s like a \u00ab\u00a0stop now\u00a0\u00bb signal. If a task is interrupted, any ongoing work is discarded, and control shifts to the boundary event&rsquo;s path.<\/p>\n<p>A <strong>non-interrupting boundary event<\/strong> runs in parallel. It doesn\u2019t stop the parent task \u2014 it executes alongside it. This is ideal for timeouts or cancellations that don&rsquo;t prevent the main task from finishing.<\/p>\n<p>Choosing the wrong type can cause processes to hang, fail to complete, or behave unpredictably under load.<\/p>\n<h3>When to Use Which Type<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Use Case<\/th>\n<th>Recommended Type<\/th>\n<th>Why<\/th>\n<\/tr>\n<tr>\n<td>Timeout after 30 seconds<\/td>\n<td>Non-interrupting<\/td>\n<td>Let the task continue; just add a delay warning.<\/td>\n<\/tr>\n<tr>\n<td>Cancel the process if user aborts<\/td>\n<td>Interrupting<\/td>\n<td>Stop all work immediately.<\/td>\n<\/tr>\n<tr>\n<td>Log error after task fails<\/td>\n<td>Non-interrupting<\/td>\n<td>Allow task to complete, then handle error.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Using the wrong type leads to unintended side effects. I\u2019ve seen a payment processing flow hang for 30 seconds because a non-interrupting timeout was mistakenly modeled as interrupting.<\/p>\n<h2>Event Sub-Processes: The Hidden Trap<\/h2>\n<p>Event subprocesses are often misunderstood. They\u2019re not a substitute for boundary events \u2014 they\u2019re a way to model global, asynchronous responses.<\/p>\n<p>They should be used when an event can fire from anywhere in the process, not just from a specific activity. For example, a \u00ab\u00a0System Outage\u00a0\u00bb event subprocess should trigger regardless of which task is active.<\/p>\n<p>But the mistake? Applying an event subprocess to a single task when a boundary event would suffice. This overcomplicates the model and introduces unnecessary execution paths.<\/p>\n<h3>When an Event Sub-Process Is Actually Wrong<\/h3>\n<ul>\n<li>Using an event subprocess to catch an error that only occurs in one task \u2014 better to use a boundary event.<\/li>\n<li>Modeling a timer on a single task with an event subprocess instead of a boundary event.<\/li>\n<li>Creating an event subprocess for a cancellation that only applies in a specific path \u2014 it should be local to that path.<\/li>\n<\/ul>\n<p>Event subprocesses are for <em>global<\/em> responses \u2014 things that can happen at any time, from any point, and affect the entire flow. If the event is tied to a specific task or path, a boundary event is the right choice.<\/p>\n<h2>Correct Patterns for Error, Time, and Cancellation Handling<\/h2>\n<p>Many teams misuse boundary events because they don\u2019t understand the <strong>semantic intent<\/strong> behind each type. Here are the correct patterns.<\/p>\n<h3>For Timeouts: Non-Interrupting Timer Boundary Events<\/h3>\n<p>If a task must complete within a time limit, use a non-interrupting timer boundary event to trigger a timeout path.<\/p>\n<p>This allows the task to continue running while the timeout is monitored. It\u2019s ideal for customer service workflows, where you want to escalate if no response is received within 5 minutes.<\/p>\n<p>Do not use an interrupting timer \u2014 unless you truly want to stop the task immediately.<\/p>\n<h3>For Cancellations: Interrupting Cancel Boundary Events<\/h3>\n<p>Use an interrupting cancel boundary event when a user or system explicitly cancels the process.<\/p>\n<p>This is common in order management or approval flows. The moment a \u00ab\u00a0Cancel\u00a0\u00bb event is triggered, the entire task or subprocess stops, and the cancellation path is taken.<\/p>\n<p>Ensure the cancel boundary event is connected to the correct point in the flow \u2014 usually the start of the task or subprocess.<\/p>\n<h3>For Errors: Error Boundary Events<\/h3>\n<p>Use error boundary events when an error occurs within a task and you want to handle it locally. This is the standard way to model exception handling.<\/p>\n<p>Always include an error code or message in the label (e.g., \u00ab\u00a0Error: Invalid Credit Card\u00a0\u00bb). This makes the behavior explicit and traceable.<\/p>\n<p>Never attach an error boundary event to a task that doesn\u2019t throw an error. It will never trigger \u2014 and that breaks the model\u2019s logic.<\/p>\n<h2>When to Avoid Boundary Events Altogether<\/h2>\n<p>Not every deviation needs a boundary event. Sometimes, a simple exception flow is clearer and more maintainable.<\/p>\n<p>Consider this: if the exception path is triggered only once per process and is part of the main logic, use a standard error flow. Boundary events are for asynchronous, global, or time-based conditions.<\/p>\n<p>Overusing boundary events creates a model that\u2019s hard to follow, harder to debug, and more likely to contain unintended behavior.<\/p>\n<h3>Decision Checklist: Use Boundary Event or Exception Flow?<\/h3>\n<ol>\n<li>Is the condition tied to a specific task or path? \u2192 Use exception flow.<\/li>\n<li>Does the event occur at any time, regardless of context? \u2192 Use event subprocess.<\/li>\n<li>Is it a timeout or cancellation? \u2192 Use non-interrupting or interrupting boundary event accordingly.<\/li>\n<li>Is the event a response to external input (e.g., email, message)? \u2192 Use event subprocess.<\/li>\n<\/ol>\n<p>If you\u2019re unsure, ask: \u201cWould this trigger even if the task had already finished?\u201d If yes, it\u2019s a candidate for an event subprocess. If not, re-evaluate your modeling choice.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I use multiple boundary events on the same task?<\/h3>\n<p>Yes \u2014 but only if they represent different types of conditions (e.g., a timer and an error). Use non-interrupting for parallel behaviors. Avoid interrupting boundary events unless you\u2019re certain about the execution order.<\/p>\n<h3>Why is my process not completing when I use a boundary event?<\/h3>\n<p>Most likely, you used an interrupting boundary event on a task that should continue. The process stops when the boundary event triggers, but the parent task never resumes. Use non-interrupting events for timeouts and error handling.<\/p>\n<h3>When should I use an event subprocess instead of a boundary event?<\/h3>\n<p>Use an event subprocess when the event can occur from any point in the process, such as a system alert, external message, or global cancellation. Use boundary events for task-specific responses.<\/p>\n<h3>Can I use a boundary event to model a retry mechanism?<\/h3>\n<p>Not directly. Use a loop marker or a multi-instance task for retries. A boundary event can trigger a retry path, but it should not be the primary mechanism. Model retry logic via loop conditions and error handling.<\/p>\n<h3>What\u2019s the difference between a boundary event and a start event?<\/h3>\n<p>A start event begins a process. A boundary event is attached to an activity and triggers during its execution. They serve entirely different roles \u2014 one starts, the other interrupts.<\/p>\n<h3>Why use a non-interrupting boundary event instead of an error flow?<\/h3>\n<p>Use non-interrupting events when you want to monitor a condition (e.g., timeout) while the task keeps running. Use error flows when the error is part of the task\u2019s natural failure path.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Boundary events are powerful, but their misuse can introduce hidden logic that breaks process behavior. I&rsquo;ve seen teams deploy processes that fail silently because a boundary event was attached to the wrong task or triggered in an unintended context. The root issue? Confusion between interrupting and non-interrupting behavior, and failing to recognize when a simple [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":571,"menu_order":5,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-577","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>BPMN Boundary Event Mistakes: Fixing Common Errors<\/title>\n<meta name=\"description\" content=\"Fix common BPMN boundary event mistakes with proven patterns for error handling, timeouts, and cancellations. Learn when and how to use them correctly.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Boundary Event Mistakes: Fixing Common Errors\" \/>\n<meta property=\"og:description\" content=\"Fix common BPMN boundary event mistakes with proven patterns for error handling, timeouts, and cancellations. Learn when and how to use them correctly.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/\",\"name\":\"BPMN Boundary Event Mistakes: Fixing Common Errors\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:20:37+00:00\",\"description\":\"Fix common BPMN boundary event mistakes with proven patterns for error handling, timeouts, and cancellations. Learn when and how to use them correctly.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Notation Misuse and Semantic Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Event Sub-Processes and Boundary Events Used Incorrectly\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Boundary Event Mistakes: Fixing Common Errors","description":"Fix common BPMN boundary event mistakes with proven patterns for error handling, timeouts, and cancellations. Learn when and how to use them correctly.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/","og_locale":"fr_FR","og_type":"article","og_title":"BPMN Boundary Event Mistakes: Fixing Common Errors","og_description":"Fix common BPMN boundary event mistakes with proven patterns for error handling, timeouts, and cancellations. Learn when and how to use them correctly.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/","name":"BPMN Boundary Event Mistakes: Fixing Common Errors","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:20:37+00:00","description":"Fix common BPMN boundary event mistakes with proven patterns for error handling, timeouts, and cancellations. Learn when and how to use them correctly.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/bpmn-boundary-event-mistakes\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Notation Misuse and Semantic Errors","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-notation-mistakes\/"},{"@type":"ListItem","position":4,"name":"Event Sub-Processes and Boundary Events Used Incorrectly"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/577","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/577\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/571"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=577"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=577"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}