Ingo Richtsmeier

We should consider to output this only once on the process level. It may confuse people when they get a lot of false positive messages here.

As a follow-up: I've seen the issue mentioned in the release 0.8.0, and I'm wondering if the dependency to the script-worker, that is introduced here, is documented anywhere? Maybe it's...

@hkupitz and @jonathanlukas, all Zeebe clients always require a correlation key for publishing messages. My assumption is, that we need a new command for the GRPC spec like `publishStartMessage` where...

>it works on zeebe side May be. But in the Java client I have to write ``` zeebeClient.newPublishMessageCommand().messageName(messageName).correlationKey(correlationKey) ``` before I can add `.send()`. And zbctl says ``` $ zbctl...

Even if we don't implement it now, we should keep the issue open to check if this modeling style in Camunda 7 happened any other time.

As the documented result of an in-person discussion with @ingorichtsmeier and @jonathanlukas, I added this pull request: #225. It is expected to change and help us find the best APIs...

This is a good topic for the community summit hackday. It covers SPIN expressions, Scripts and more.

Taking a look at the Camunda 7 implementation (https://docs.camunda.org/rest/camunda-bpm-platform/7.20/#tag/Message/operation/deliverMessage), they provide process variables in the response as well (if requested). Would that be feasible for Zeebe as well? It will...

Sidenote: Another wish to close a product gap: synchronous signal sending. Camunda 7 returns an empty payload: https://docs.camunda.org/rest/camunda-bpm-platform/7.20/#tag/Signal. I could create a new gap/epic/feature request, if you tell that it...

> signals work quite differently from messages in Zeebe Thank you for the confirmation