Intermediate Catch Event Not Progressing in Operate but Tasklist Tasks Continue

Camunda 8 Topics
,
1

Hi Camunda Community,

I’m facing an issue with my process model in Camunda 8 (SaaS), where an Intermediate Catch Event appears to be stuck in Operate. However, the process continues as expected in the Tasklist, and I can complete subsequent tasks. This inconsistency is making it difficult to monitor the process in Operate.

Issue Description

  • I have a process model with a Message Intermediate Catch Event.
  • The Tasklist shows the tasks correctly after the Intermediate Catch Event.
  • In Operate, the process instance does not progress beyond the Intermediate Catch Event. It gets stuck there, even though the rest of the process is running in the background.
  • The issue occurs when sending a message with a correlation key from a worker (implemented using Spring Boot).

What I Have Tried

  1. Configuration Validation:
  • Verified that the correlation key (employeeNumber) and message name (FormularWeiterleitung) are set correctly in the BPMN model.
  • Ensured the global message reference and the subscription correlation key in the BPMN model are correctly configured.
  1. Worker Implementation:
  • The worker successfully sends the message using the client.newPublishMessageCommand(). Below is the relevant snippet:
client.newPublishMessageCommand()
    .messageName("FormularWeiterleitung")
    .correlationKey(employeeNumber)
    .variables(variables)
    .send()
    .join();

Enabled DEBUG logs for io.camunda.zeebe in application.yaml

camunda:
  client:
    mode: saas
    auth:
      client-id: xxxxxxxxxx
      client-secret:xxxxxxxxx
    cluster-id: xxxxxxxxxx
    region: bru-2
    zeebe:
      defaults:
        stream-enabled: false
  operate:
    base-url:xxxxxxx            # URL für Camunda Operate
    auth:
      client-id: xxxxxxxxxx               # Client ID für Operate
      client-secret: xxxxxx

spring:
  mail:
    host: smtp.gmail.com
    port: 587
    username: xxxxxxx
    password: xxxxxxxxx
    properties:
      mail:
        smtp:
          auth: true
          starttls:
            enable: true

logging:
  level:
    io.camunda.zeebe: DEBUG
    org.springframework.mail: Debug
  • Verified that the message is published and no errors are shown in the logs.
    • Elasticsearch logs indicate that the process instance is running, and the message is correlated successfully.
  1. Testing Without Spring Email:
  • Initially, the process was stuck at the Intermediate Catch Event when sending an email using Spring’s JavaMailSender.
  • Removing the Spring Email logic from the worker allowed Operate to progress further. However, this is not a sustainable solution since email functionality is required.

Environment Details

  • Camunda Version: 8 (SaaS)
  • Worker Framework: Spring Boot with the Zeebe Java Client (8.6.5)
  • Elastic Search: Enabled and operational.
  • Operate URL: https://bru-2.operate.camunda.io/<cluster-id>/operate

Questions

  1. What could be causing the Intermediate Catch Event to appear stuck in Operate but progress in the Tasklist?
  2. Are there any additional configurations required in application.yaml or BPMN for this scenario, especially when using Spring Email alongside Camunda?
  3. Could this be related to message correlation or potential misalignment between Operate and Tasklist in the SaaS environment?

Any guidance or suggestions would be greatly appreciated. Let me know if you need more details or logs.

Thanks in advance for your support!

image

2

Hi @abi1014 - can you share your BPMN model also? You can attach it as a reply.