+3Hi, We have a BPA when the planned start date is updated for the first work task (minimum task sequence) on a given work order, it will update the remaining work tasks planned start date with the same date.
If there are 20 or less work tasks in the work order, then this works as expected. If there are more than 20 records to be updated, then get the following error.
Any ides whether this is a restriction/limitation?
20 is the default number of workflows that can be cascaded. This is an editable configuration in bpa_system_settings_tab. Try adding “Variable” as “CASCADE_LIMIT” and “Value” as a higher number which suites your scenario. If it doesn’t work right away, try restarting the OData container and rechecking.
But keep in mind, all these workflows will run in a single transaction. If the workflow load is too much, you will face issues like transaction timeout. If issues like this arise, you will have to turn the workflow execution into async.
hello
where in IFScloud can we found this bpa_system_settings_tab ?
thank you in advance
best regards
You can’t do this change in the browser. You will have edit the table values of the the database table itself.
+5This issue has been addressed by removing the 20 cascade limit from IFS Cloud 24R2 onwards. Without restricting the number of Workflows that can be executed in a cascaded manner, Workflow execution is now limited to a time limit.
Synchronous Workflows - 5 minutes
Asynchronous Workflows - 15 minutes
Within these time limits, any number of Workflows can be executed using the default resources available in IFS Cloud, without disrupting the system. The time limits can be changed in BPA_SYSTEM_SETTINGS_TAB as appropriate to the environment configurations.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
