Message event error: EXTRACT_VALUE_ERROR

Camunda 8 Topics Discussion & Questions
1

Hi, I’m playing around with zeebe-node library and faced an issue which I’m not able to resolve. In my workflow, there is a message event, which should be triggered by the client. I believe I’m sending the correct message to the broker but It’s raising an incidence { Error Type: EXTRACT_VALUE_ERROR, Error Message: Failed to extract the correlation-key by ‘worker1Id’: no value found }. I’m using correct correlation key and message name.

following is my message event listener:
<bpmn:message id=“Message_01t2tpj” name=“worker1_status”>
bpmn:extensionElements
<zeebe:subscription correlationKey=“worker1Id” />
</bpmn:extensionElements>
</bpmn:message>

Event trigger:
await this._zbClient.publishMessage({
correlationKey: ‘worker1Id’,
messageId: uuid.v4(),
name: ‘worker1_status’,
variables: { status: ‘PROCESSED’ },
timeToLive: 10000,
});

I’m not sure where the issue is and if someone can help or direct me to an appropriate forum, that will be appreciated.

Thanks,

2

At first sight, it sounds like an issue… Is it possible for you to create a simple reproducer and open an issue for it?

3

Hey @shantanubhusari @salaboy ,

I think the problem is that the correlationKey naming is maybe a bit confusing, see also this issue https://github.com/zeebe-io/zeebe/issues/2718 .

@shantanubhusari you need to have variable worker1Id in your running worklfow instance. The message is then correlated to this instance with the same value.

Does this make sense to you guys?

Greets
Chris

1 Like
4

@Zelldon that makes a lot of sense… I gave my thumbs up for correlationExpression in the GitHub issue. From the error report here it really looks confusing.

1 Like
5

Hi @shantanubhusari, please read this: https://zeebe.io/blog/2019/08/zeebe-message-correlation/

Particularly the “Common Mistakes” section. It is covered in there. Please comment on the linked issue to have the field renamed to correlationValue if you think that would make it clearer.

Josh

6

Thank you everyone for the response, and the solution worked. I’ve also responded to the issue to use correlationValue.

3 Likes
7