Community
Best practice regarding flows that should not be run in parallel with itself?
Some flows are perfectly fine to run in parallel with itself.
Feature request: Use a generic or assignable username for flows triggered by timer
In /admin/processes the column "User" shows
Possibility to change the 5 minute limit of "Short running synchrone (non persistent) workflows"?
We have a subflow consisting of a few tasks, that takes anything from 1 to approx 9 minutes to finish.
Feature request: Implement retry cycles for servicetasks (failedJobRetryTimeCycle)
It would be great if we could use the Camunda function "retry cycle" in Onify to retry a task, that sometimes fails, a specified number of times with a specified time apart. Now we need to build this logic ourselves around tasks that need such "safety net" to not exit a full flow because of some intermittent downtime or unreliable service e t c. 😊
How does Error Boundary Event on a task work in Onify?
I'm looking at a BPMN flow with 11 tasks with onifyApiRequest and 6 of them has got an "Error Boundary Event"-marker on them. There is no added information in the panel for any of them. I assume if there is some error in one of them this flow will just jump to the End?
What makes flows sometimes end up "running" for infinity and how do we handle it?
I sometimes see flows "hanging" and end up running for infinity.
What are the most common reasons for this happening?
Can we get flows triggered by schedule/timer in the logs?
As far as I can see only flows triggered by users are visible in the log, except for the flow "sync-resources.bpmn" which is triggered by "app".