Community
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.
When calling any subflow with /api/v2/my/workflows/run/{key} it is limited to a runtime of 5 minutes before it fails as of <https://support.onify.co/reference/postmyworkflowsrunkey>
This seems to be a hardcoded value, and probably set to be enough for most of such task. But having such a limit will in our case force us to move the logic from a subflow to our main flow to not have timeouts, which is unfortunate in terms of maintainability etc.
Is there any possibility to change set this limit to another value within our own Onify instance?
In return I can provide you with an enhanced and more reliable version of this blueprint. ;)
<https://github.com/onify/blueprint-cloudblue-commerce-change-subscription>
Posted by Dennis 3 months ago
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. 😊
![](https://files.readme.io/5cf3f89-image.png)
\<bpmn:serviceTask id="sendEmailTask" name="Send Email Task"
camunda:asyncBefore="true"
camunda:failedJobRetryTimeCycle="R3/PT30S">
\</bpmn:serviceTask>
Posted by Dennis 3 months ago
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?
For what type of errors will this happen - anything else than a statuscode 200? Is it configurable?
Is any of the additional fields usable in Onify?
![](https://files.readme.io/a558032-image.png)
Posted by Dennis 4 months ago
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?
Is it recommended to check running flows periodically and stop old ones?
What happens if we don't - is there a maximum number of running flows etc?
Would it be a good idea to create a flow "purge-old-running-processes.bpmn" which stops the one that are X days old, and even send a report about it by mail so that we have some info about which ones it concerns and how often it happens?
(I know about the possibility to make a flow "nonpersistent", that will automatically stop it after a while , but it might not be possible to use if the flows needs to return an output.)
Posted by Dennis 5 months ago
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".
It might clog the log a little if we got all the scheduled flows in the log, but if we do want to be able to find problems with the scheduled flows it would be good to be able to see them in the log as well.
Is it in some way possible to configure, by flow, if you want it to be logged or not? :)
Posted by Dennis 5 months ago
How do I run onifyElevatedApiRequest from a script task?
I am trying to run `onifyElevatedApiRequest` from a script task using users token but it does not work. Is it possible to run from a script task?
This is what I am trying to do:
```javascript
let onifyHeaders = {
'Content-Type': 'application/json',
'Authorization': environment.settings.authorization
}
var resourceOptions = {
url: `admin/resources/file?stream=false&path=${templatePath}`,
headers: onifyHeaders
}
let result = await environment.services.onifyElevatedApiRequest(resourceOptions);
```
Posted by Robert Lundsten almost 3 years ago