Josep Piguillem e14f445e6b fix(api): retry commands that clash with a concurrent write ...

Services run commands through a CommandRunner that runs one again (up to
5 times, waiting a little longer each time) when its aggregate changed
underneath, e.g. a saga writing to the same ticket. Each command loads its
aggregate fresh and stores its events in one transaction, so a
ConcurrencyError means nothing was stored and running it again is safe.
People no longer get a 409 for it, and the e2e suite stops flaking.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-15 14:00:08 +02:00

..

application

fix(api): retry commands that clash with a concurrent write

2026-10-15 14:00:08 +02:00

domain

feat: public projects, project deletion and sagas

2026-10-07 07:04:20 +02:00

infrastructure

feat: uuid ids everywhere, pickers for linked tickets, @pi/ui checkboxes

2026-10-14 19:16:43 +02:00

presenters

feat: public projects, project deletion and sagas

2026-10-07 07:04:20 +02:00