{"id":406,"date":"2026-02-25T10:17:27","date_gmt":"2026-02-25T10:17:27","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/"},"modified":"2026-02-25T10:17:27","modified_gmt":"2026-02-25T10:17:27","slug":"bpmn-boundary-events-exception-handling","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/","title":{"rendered":"Handling Exceptions and Boundary Events"},"content":{"rendered":"

When a process fails to proceed because of an unexpected event, it\u2019s rarely the user\u2019s fault\u2014it\u2019s the model that\u2019s missing a safety net. I\u2019ve seen too many diagrams collapse under real-world conditions because they assumed everything would go as planned.<\/p>\n

That\u2019s where BPMN boundary events come in. They don\u2019t just catch errors\u2014they provide a structured, visual way to respond when things go sideways, allowing you to model exceptions, timeouts, and alternate flows with precision.<\/p>\n

This chapter is your guide to mastering BPMN exception handling through boundary events. You\u2019ll learn how to integrate error events BPMN into your process flows, create alternate flows that adapt to failure, and ensure your models reflect real operational behavior\u2014not idealized theory.<\/p>\n

Understanding BPMN Boundary Events<\/h2>\n

Boundary events are attached to activities and are triggered when a specific condition occurs during the execution of that activity. Unlike standard events that sit on their own, boundary events are tethered to a task or subprocess and react to interruptions.<\/p>\n

They\u2019re the most visible form of reactive logic in BPMN. Think of them as alarms that go off when something unexpected happens\u2014like a payment failing, a document expiring, or a system timeout.<\/p>\n

There are two main types of boundary events:<\/p>\n

  • Interrupting boundary events<\/strong>\u2014Cancel the parent activity and trigger an alternate flow.<\/li>\n
  • Non-interrupting boundary events<\/strong>\u2014Run in parallel without stopping the main flow.<\/li>\n

    For error handling, interrupting boundary events are usually the right choice. They allow you to pause the process and act when something goes wrong.<\/p>\n

    When to Use Boundary Events<\/h3>\n

    Not every exception needs a boundary event. Ask yourself: does this error change the flow of the process? If yes, a boundary event is likely appropriate.<\/p>\n

    Common use cases include:\n <\/p>\n

  • Timeouts on long-running tasks (e.g., customer onboarding)<\/li>\n
  • Validation failures (e.g., missing documents)<\/li>\n
  • System errors (e.g., API failure, database timeout)<\/li>\n
  • External events (e.g., a customer cancels the request)<\/li>\n

    These aren\u2019t just exceptions\u2014they\u2019re real-world decisions that impact the process. Boundary events give you the control to respond.<\/p>\n

    Implementing Error Events BPMN<\/h2>\n

    Let\u2019s walk through a real-world example: a loan application process.<\/p>\n

    The main path assumes the applicant submits all documents on time. But what if they don\u2019t?<\/p>\n

    You can model this using an interrupting boundary event on the “Review Documents” task, linked to an error event symbol.<\/p>\n

    Here\u2019s how to set it up:<\/p>\n

      \n
    1. Place a boundary event on the “Review Documents” task.<\/li>\n
    2. Set the event type to Error Event<\/strong>.<\/li>\n
    3. Define the error code, such as “MISSING_DOCUMENT” or “INVALID_FILE.”<\/li>\n
    4. Connect the boundary event to an “Request Additional Documents” task.<\/li>\n<\/ol>\n

      This creates a clean, visual path for handling a critical failure. The main flow continues only when the error is resolved.<\/p>\n

      Key insight: error events BPMN are not just about catching bugs. They\u2019re about modeling business rules\u2014what happens when a condition is met, and who should act.<\/p>\n

      Choosing the Right Error Type<\/h3>\n

      Not all errors are the same. Use BPMN\u2019s error codes to distinguish between:\n <\/p>\n

    5. Recoverable<\/strong> (e.g., temporary system outage)<\/li>\n
    6. Non-recoverable<\/strong> (e.g., invalid ID submitted)<\/li>\n
    7. External<\/strong> (e.g., customer withdraws application)<\/li>\n

      Assigning specific error codes prevents ambiguity and helps tools or automation systems respond correctly.<\/p>\n

      For example:<\/p>\n\n\n\n\n\n\n
      Error Code<\/th>\nMeaning<\/th>\nRecommended Flow<\/th>\n<\/tr>\n
      DOCUMENT_EXPIRED<\/td>\nSubmitted document is outdated<\/td>\nRequest renewal<\/td>\n<\/tr>\n
      API_TIMEOUT<\/td>\nService didn\u2019t respond<\/td>\nRetry or escalate<\/td>\n<\/tr>\n
      INVALID_CREDENTIALS<\/td>\nUser authentication failed<\/td>\nBlock or redirect<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      These codes become part of the model\u2019s logic\u2014no more guesswork.<\/p>\n

      Modeling BPMN Alternate Flows<\/h2>\n

      When you introduce error events, you\u2019re not just adding a failure path\u2014you\u2019re building a full decision tree.<\/p>\n

      BPMN alternate flows are not just for exceptions. They\u2019re for any situation where the process branches based on conditions.<\/p>\n

      Here\u2019s how to structure them:<\/p>\n

        \n
      • Use boundary events<\/strong> on tasks for reactive error handling.<\/li>\n
      • Use gateways<\/strong> for conditional decisions based on data or status.<\/li>\n
      • Keep the main flow clean and focused on success.<\/li>\n<\/ul>\n

        Example: A customer service ticket process.<\/p>\n

        The “Assign Agent” task has a boundary event for “Agent Unavailable” (error event). When triggered, it branches to “Reassign to Backup Team.”<\/p>\n

        This is a classic case of BPMN alternate flows. The model reflects that not every ticket goes to the same agent\u2014and that\u2019s okay. It\u2019s how real teams work.<\/p>\n

        Best Practices for Alternate Flows<\/h3>\n

        Don\u2019t let alternate flows clutter your diagram. Here\u2019s how to keep them effective:<\/p>\n

          \n
        • Limit to 1\u20132 error paths per task<\/strong>\u2014More than that, and complexity overwhelms clarity.<\/li>\n
        • Use descriptive labels<\/strong>\u2014E.g., “Payment Failed” not just “Error.”<\/li>\n
        • Group similar errors<\/strong>\u2014Use a single boundary event for multiple similar failures.<\/li>\n
        • Document error codes<\/strong>\u2014Add a note or legend for stakeholders who may not know the model.<\/li>\n<\/ul>\n

          Remember: the goal is communication, not perfection. A clean, readable model is more valuable than one that\u2019s technically correct but impossible to follow.<\/p>\n

          Advanced Tips: Non-Interrupting Events and Timers<\/h2>\n

          Not all boundary events stop the main flow. Non-interrupting events run in parallel, which is useful for monitoring or logging.<\/p>\n

          For example, a “Monitor Processing Time” non-interrupting boundary event can track how long a task takes. If it exceeds 30 minutes, it logs an alert\u2014but the task still completes.<\/p>\n

          Timer events are another powerful tool for exceptions. A timer boundary event can trigger a retry or escalation after a set period.<\/p>\n

          Use case: “Verify Identity” task with a 5-minute timer. If no response, the system escalates to a supervisor.<\/p>\n

          This kind of logic is standard in customer service, finance, and logistics\u2014where time is a factor, and delays must be managed.<\/p>\n

          Common Pitfalls and How to Avoid Them<\/h2>\n

          Even experienced modelers make mistakes. Here are the most common issues with BPMN boundary events\u2014and how to fix them:<\/p>\n

            \n
          • Overusing boundary events<\/strong>\u2014Only attach them when you genuinely need to respond. Most tasks don\u2019t need error handling.<\/li>\n
          • Using generic error labels<\/strong>\u2014Avoid “Error” or “Error Event.” Be specific: “API Connection Failed.”<\/li>\n
          • Forgetting to handle the recovery flow<\/strong>\u2014An error path must lead to a resolution. Don\u2019t leave it open-ended.<\/li>\n
          • Confusing interrupting vs. non-interrupting<\/strong>\u2014Interrupting stops the task. Non-interrupting runs alongside. Use the right one.<\/li>\n<\/ul>\n

            As you grow in confidence, revisit your models and ask: does this event add value? If not, remove it. Simplicity is power.<\/p>\n

            Frequently Asked Questions<\/h2>\n

            What is a BPMN boundary event?<\/h3>\n

            A boundary event is an event attached to a task or subprocess that triggers when a specific condition occurs during its execution\u2014such as an error, timeout, or external signal.<\/p>\n

            How do I use error events BPMN in a real workflow?<\/h3>\n

            Place an interrupting boundary event on a task, set it to an error event, define the error code, and link it to a recovery task. For example, use it to request missing documents in a loan approval process.<\/p>\n

            Can I use multiple boundary events on the same task?<\/h3>\n

            Yes, but keep it simple. Use one for critical errors and another for monitoring (e.g., timeout). Avoid more than two to prevent confusion.<\/p>\n

            What\u2019s the difference between a boundary event and a gateway?<\/h3>\n

            A gateway determines the next step based on a condition. A boundary event reacts to an external trigger *during* task execution. They serve different purposes: decision vs. interruption.<\/p>\n

            When should I use non-interrupting boundary events?<\/h3>\n

            Use them when you want to monitor or log an event without stopping the main task\u2014like tracking processing time or sending a reminder.<\/p>\n

            How do I handle BPMN alternate flows without cluttering the diagram?<\/h3>\n

            Limit to 1\u20132 key alternate flows per task. Use clear labels, keep the main path simple, and document error codes in a legend for clarity.<\/p>\n","protected":false},"excerpt":{"rendered":"

            When a process fails to proceed because of an unexpected event, it\u2019s rarely the user\u2019s fault\u2014it\u2019s the model that\u2019s missing a safety net. I\u2019ve seen too many diagrams collapse under real-world conditions because they assumed everything would go as planned. That\u2019s where BPMN boundary events come in. They don\u2019t just catch errors\u2014they provide a structured, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":402,"menu_order":3,"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-406","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nBPMN Boundary Events: Handle Exceptions with Confidence<\/title>\n<meta name=\"description\" content=\"Learn how to use BPMN boundary events for robust error handling, alternate flows, and responsive process modeling. Master error events BPMN and build resilient workflows.\" \/>\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\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Boundary Events: Handle Exceptions with Confidence\" \/>\n<meta property=\"og:description\" content=\"Learn how to use BPMN boundary events for robust error handling, alternate flows, and responsive process modeling. Master error events BPMN and build resilient workflows.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/\",\"name\":\"BPMN Boundary Events: Handle Exceptions with Confidence\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:17:27+00:00\",\"description\":\"Learn how to use BPMN boundary events for robust error handling, alternate flows, and responsive process modeling. Master error events BPMN and build resilient workflows.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BPMN Fundamentals for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Building Realistic Process Models\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Handling Exceptions and Boundary Events\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Boundary Events: Handle Exceptions with Confidence","description":"Learn how to use BPMN boundary events for robust error handling, alternate flows, and responsive process modeling. Master error events BPMN and build resilient workflows.","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\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/","og_locale":"id_ID","og_type":"article","og_title":"BPMN Boundary Events: Handle Exceptions with Confidence","og_description":"Learn how to use BPMN boundary events for robust error handling, alternate flows, and responsive process modeling. Master error events BPMN and build resilient workflows.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/","name":"BPMN Boundary Events: Handle Exceptions with Confidence","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:17:27+00:00","description":"Learn how to use BPMN boundary events for robust error handling, alternate flows, and responsive process modeling. Master error events BPMN and build resilient workflows.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-boundary-events-exception-handling\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"BPMN Fundamentals for Beginners","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Building Realistic Process Models","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/"},{"@type":"ListItem","position":4,"name":"Handling Exceptions and Boundary Events"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/406","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/406\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/402"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=406"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=406"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}