Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does IntermediateCatchEvent Element supported? #183

Open
shujer opened this issue Feb 29, 2024 · 3 comments
Open

Does IntermediateCatchEvent Element supported? #183

shujer opened this issue Feb 29, 2024 · 3 comments

Comments

@shujer
Copy link

shujer commented Feb 29, 2024

hi, master, I try to use servicetak + IntermediateCatchEvent to handle some callback service task,but seems signal doesn't work.
The process was blocked by wait message, if I use userTask the signal API works well.

@paed01
Copy link
Owner

paed01 commented Feb 29, 2024

Have you tried signaling with the Signal Id? The intermediate catch event id won’t work.

@shujer
Copy link
Author

shujer commented Feb 29, 2024

any different usage of signal between userTask and IntermediateCatchEvent?

I trigger by engine.execution.signal({id: "IntermediateCatchEvent_id"}), which IntermediateCatchEvent_id is same as the id in bpmn definition element. how to get Signal Id?

@paed01
Copy link
Owner

paed01 commented Mar 4, 2024

Not sure how your flow is designed.

The behaviour differs, a user task can be signaled before it is running since it collects signals by default. An "empty" intermediate catch event, i.e. without an event definition (signal, message, timer, etc), will have to be running before it can be signaled with id to continue.

An intermediate catch event defined as a signal or message will have a reference in the source Xml to a Signal- or Message-element with an id that can be used to signal the flow.

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

No branches or pull requests

2 participants