Hi @heril.muratovic06 - because of Zeebe’s asynchronous and eventually consistent event driven design, there will always be at least a slight delay between an action occurring in the process and the data being exported to Operate and the APIs. However, there are some improvements to this coming in the near future:
- we are working on user task listeners (search “user task listener” on roadmap.camunda.com to see all the features); for most use cases needing near-real-time data about user tasks, user task listeners will likely be a good solution. These are targeted for release in 8.8 later this year.
- we are also working on a real time, read-only API within Zeebe to fetch process data directly, bypassing the exporter for some process data.
From your description, I assume you’re using a custom tasklist application and that’s why the export delay is causing headaches in your frontend. Are you using Camunda Forms as well, or are your forms built into your application? While it isn’t the best idea, and not semantic BPMN, you could also look at replacing your user tasks with service tasks and pushing the data to your application via job workers.
Another user I worked with had similar issues when building a custom frontend, and this thread has a lot of good information as well: There's a delay after a process instance is started. They went with the job worker route until user task listeners are generally available.