Skip to main content
Solved

BPA data limitation error when inspecting (creation process debug)

  • November 21, 2025
  • 5 replies
  • 23 views

REOGIRARD
Sidekick (Customer)
Forum|alt.badge.img+8

 Hello,

I’m working on a workflow which :
-  create catalog / inv / purchase / sales part on different sites
- create routing and product structure, work guidelines and fill those with an original shop order / sales part datas
- create a supplier for purchase part link and create price list element
 

Link of png of the bpa as i can’t upload directly here : https://ibb.co/wrQvL9ZT


This include a lot of API GET calls to get data to construct POST calls, and to control state of data for logic control.

I’m getting the following error when I try to inspect it (to finish to build the workflow) :

“It took long time to inspect the Workflow. Please limit the amount of data and try again.”

How am I supposed to avoid this ?

Thank you

Best answer by N.GEORGI

@REOGIRARD  in your get api, try to limit the number of field your are fetching using $select

make sure your api are responsive.

 

If you encounter memory issue after : 

Remove variables if they are no longer used via execution.removeVariable().

5 replies

Forum|alt.badge.img+6
  • Sidekick (Customer)
  • Answer
  • November 21, 2025

@REOGIRARD  in your get api, try to limit the number of field your are fetching using $select

make sure your api are responsive.

 

If you encounter memory issue after : 

Remove variables if they are no longer used via execution.removeVariable().


REOGIRARD
Sidekick (Customer)
Forum|alt.badge.img+8
  • Author
  • Sidekick (Customer)
  • November 21, 2025

Ok got it after testing with different dataset, it seems to be the total data fetched (little shop order with not much operations guidelines etc doesn’t trigger the error) but I have some shop orders with lot of operations, operations guidelines etc …

Is cutting out the whole BPA in few little workflows can avoid this error ?
It would be easier to read and maintain aswell with each workflow his own single responsibility


Forum|alt.badge.img+6
  • Sidekick (Customer)
  • November 21, 2025

I don’t think using multiple workflow would solve the problem cause there is no commit, which mean that all data will be still in memory.

 

you can try to get the data using multiple call and filters then joining the collections using a script task :

 

var ArrayList = Java.type('java.util.ArrayList');
var list = new ArrayList();
list .addAll(Reference_CountingReportLine_Set2);
list .addAll(Reference_CountingReportLine_Set2);
execution.setVariable("YearCountingReportLine", list )

 

maybe ​@kamnlk could help on this?


Forum|alt.badge.img+9
  • Hero (Employee)
  • November 24, 2025

Hi,

@REOGIRARD  The error seems to come due to timeout happening in the workflow inspect execution

ref: Workflow Tooling - Technical Documentation For IFS Cloud

as ​@N.GEORGI  mentioned its better to use $select or reduced data set when inspecting or testing a workflow. Another way would be to try to inspect the workflow, one section at a time if the workflow is too complex. 


REOGIRARD
Sidekick (Customer)
Forum|alt.badge.img+8
  • Author
  • Sidekick (Customer)
  • November 24, 2025

Well, selecting less data from entities make it works smoother in inspection mode
In production, I don’t have issue, it’s running faster.
I will keep using the select option to reduce the data volume fetched so it will be smoother to work on the workflow after that.
Thank you for your help