đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
Details:
When we have a workflow instance in error status due to error like:
Workflow step instance threshold exceeded. Too many workflow steps were started based on your policy.
or Workflow process instance threshold exceeded. Too many workflow instances were started based on your policy.
It's not possible to follow it K2 log file (HostServer24xxx.log)
Step to reproduce:
1) Generate one of 2 issues (by reducing numbers for one workflow)
2) Go to K2 logs
Result: Nothing logs about the issue.
Note: Tested with mode "All" (with debug, information status): same issue: nothing logged.
Excepted result:
Clear error message with message like:
Workflow step instance threshold exceeded. Too many workflow steps were started based on your policy on instance 123456 because the activity XXXX has been executed last time at {date}. That exceed the current parameter YYYY steps by ZZZ minutes.
As workaround, you can put in place a workflow that will do what you want in case of error like this using the existing functionality "Start when any Workflow Errors".
With this functionality, you verify if the workflow in error state is with working "Workflow step instance threshold exceeded. Too many workflow steps were started based on your policy." (or other) and then, you can do for example:
- Log the error in a SmartBox
- and/or send mail
- and log the error on a SQL table.
- ... anything that could be done with K2 workflows.