Hi @kristoffer.jalen and @MagzhanUnited - Camunda is absolutely appropriate for customer-facing tasks, and many of our customers have processes that involved customers completing forms.
To add on to what Christian said, I would also suggest you might be solving the problem in the wrong way. First, Zeebe is asynchronous, so trying to wire up synchronous events can be difficult and may require a different solution. Second, having your application reach out to process means your application is more tightly coupled with the process. In one sense, your application shouldn’t care what step of the process you are on, because that is managed by the process engine.
Here’s a couple thoughts/questions:
- I know that during the development and testing cycle, a few seconds can feel like an eternity, but how often is that delay actually noticable to users of your application? How often are users aware that the previous step of the process had just completed and are staring at their computer screen waiting for a form to appear? (Of course I do not mean to dismiss the delay, which is long: more on that below.)
- I would recommend not using a User Task, and instead use a Service Task with either a job worker or Connector to push the task to your application, rather than your application trying to pull it. This has two benefits: first, the delay on the exporter is not a factor; and second, your application can remain further decoupled from the running process.
And again, 7-10 seconds is quite long; I experience a delay of 500ms-1s at most in my testing. @kristoffer.jalen - if you are willing, can you private message me the email for your SaaS account and/or the UUID of your organization (in the URL right after logging in)? I can check your cluster and discuss delay with our internal teams to get some further clarification there. (@MagzhanUnited - since you are using Self-Managed, the delay is much harder to identify because it depends on the environment you deployed it to, what resources are allocated to the services, etc.)