# How to handle message correlation event even if active token has not yet reached that point

**URL:** <https://forum.camunda.io/t/how-to-handle-message-correlation-event-even-if-active-token-has-not-yet-reached-that-point/66523>\
**Category:** Camunda 8 Topics\
**Created:** [January 2, 2026, 11:49am UTC](https://forum.camunda.io/t/how-to-handle-message-correlation-event-even-if-active-token-has-not-yet-reached-that-point/66523 "2026-01-02T11:49:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![firstpostcommenter](https://forum.camunda.io/letter_avatar_proxy/v4/letter/f/ad7895/32.png) [@firstpostcommenter](https://forum.camunda.io/u/firstpostcommenter)\
**Post date:** [January 2, 2026, 11:49am UTC](https://forum.camunda.io/t/how-to-handle-message-correlation-event-even-if-active-token-has-not-yet-reached-that-point/66523/1 "2026-01-02T11:49:48Z")

</div>

Hi,

Even if Camunda active token is not waiting for the message correlation, the message may come so the process should handle it.

In Camunda 7 this was handled this way:

 ![image](https://forum.camunda.io/uploads/default/original/3X/d/7/d788d8df9f1171ac22307d4a7bbe79231cd0f72f.png)

How can I do something like that in Camunda 8?

[message\_correlation.bpmn](https://forum.camunda.io/uploads/short-url/bNMWTElw2wtLM5xDTbIe5UxfmM8.bpmn) (6.9 KB)

---

<div class="post-metadata">

**Author:** ![GotnOGuts](https://forum.camunda.io/letter_avatar_proxy/v4/letter/g/b77776/32.png) [@GotnOGuts](https://forum.camunda.io/u/GotnOGuts)\
**Post date:** [January 2, 2026, 5:36pm UTC](https://forum.camunda.io/t/how-to-handle-message-correlation-event-even-if-active-token-has-not-yet-reached-that-point/66523/2 "2026-01-02T17:36:14Z")

</div>

Hi @firstpostcommenter

In C8, the expected way to handle this is to put a Time-to-Live (TTL) on the message that is being received. The non-interrupting event subprocess is not needed.

> **[Messages | Camunda 8 Docs](https://docs.camunda.io/docs/components/concepts/messages/#message-buffering)**
>
> Learn how process instances can respond to incoming messages.

The sender of the message indicates how long the message should be valid for.

---

<div class="post-metadata">

**Author:** ![claudio\_rio](https://forum.camunda.io/user_avatar/forum.camunda.io/claudio_rio/32/33171_2.png) [@claudio\_rio](https://forum.camunda.io/u/claudio_rio)\
**Post date:** [January 2, 2026, 7:28pm UTC](https://forum.camunda.io/t/how-to-handle-message-correlation-event-even-if-active-token-has-not-yet-reached-that-point/66523/3 "2026-01-02T19:28:19Z")

</div>

Conditional Events is in the roadmap for a future release, but for now you have to use TTL as mentioned by @GotnOGuts . Just make sure you consider the time the message will live in the cache and number of instances you have running to make sure the cache will support the load.

I personally like the Conditional event approach in some scenarios because you can have more than one “check point” controlled by a single message, but we have to wait until a future release.

---

<div class="post-metadata">

**Author:** ![system](https://forum.camunda.io/uploads/default/original/3X/5/8/58d50142eacca605d35cb1ef9e6b86ae85f49436.png) [@system](https://forum.camunda.io/u/system)\
**Post date:** [April 2, 2026, 7:28pm UTC](https://forum.camunda.io/t/how-to-handle-message-correlation-event-even-if-active-token-has-not-yet-reached-that-point/66523/4 "2026-04-02T19:28:34Z")

</div>

Closed on April 2, 2026, 7:28pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
