Skip to content

docs(intent): the process trigger's ProcessId write-back is crash-safe - #208

Merged
delchev merged 1 commit into
masterfrom
docs/trigger-process-id
Aug 19, 2026
Merged

docs(intent): the process trigger's ProcessId write-back is crash-safe#208
delchev merged 1 commit into
masterfrom
docs/trigger-process-id

Conversation

@delchev

@delchev delchev commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Documents the trigger ordering that lands with eclipse-dirigible/dirigible#6855 (issue eclipse-dirigible/dirigible#6815), and corrects two stale bits in the same section: the generated listener is a self-describing MessageHandler, not an @Listener, and the minted businessKeyStrategy value is stored before the instance that correlates on it starts.

🤖 Generated with Claude Code

The trigger section still described an @Listener that 'writes the instance
id back', which is the half that could fail silently: the stamped ProcessId
is the at-most-once guard, and it commits separately from the start.

Says what the listener now guarantees - the minted business key stored
before the start, every process variable riding the start payload, a
write-back no document gate can refuse, and a cancelled instance when it
still does not land - for eclipse-dirigible/dirigible#6815.
@delchev
delchev merged commit d115bfb into master Aug 19, 2026
@delchev
delchev deleted the docs/trigger-process-id branch August 19, 2026 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant