Rewrite thirteen shorter pages in plain English Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lxo4MXbp6VPoDkUrTBNXJ1
docs: compensation is a second writer the start now warns about A compensation throw event which undoes two finished activities starts both handlers, so the workflow holds a token per handler and each of them writes the same workflow aggregate. The start now says so where that aggregate has no version attribute, naming the process, the throw event and the handlers. What each engine really does was measured. Camunda 8 hands out both handler jobs at the same moment. Camunda 7 starts them one after the other, and the order it undoes them in is not stable: it sorts the subscriptions by a creation time of millisecond resolution, so two activities compensated within one millisecond are undone in the order they ran in. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0168Fox39crp8dfWkZ9W84Ub
docs: what compensation is, and what VanillaBP adds to it A compensation handler is an ordinary @WorkflowTask on every adapter, and nothing in the code or in the wikis said so. The page says what the deployment does with such a handler, what the handler is given, and why VanillaBP promises nothing about the order the handlers run in. Story 466. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0168Fox39crp8dfWkZ9W84Ub