Question

Client freezing. Too many objects.

0

Currently I have a scheduled event running every 24hrs that retrieves a large JSON response (about 60k objects), and map it to a persistent entity (import mapped) This large amount of objects does not commit, but rather is used in a subsequent microflow to apply values to other persistent entities. Due to the amount of returned objects, I had to employ an OFFSET/AMOUNT(3,000) to my retrieves (hence why im not storing it as non persistent). I’m finding that when I trigger this microflow that does all the work above, from the UI, the app (browser) tab freezes. It also runs as a scheduled event, and when it runs, the client is fine (is this because its being run on server from where it was called, vs sending data back to client if I trigger the mf from the UI?)

asked 2020-09-02

Andrew Faria

2 answers

1

Hi Andrew,

When you are running scheduled event, it will be running in the background so, user experience will not be affected.

User can still continue to use the system and Scheduled event will run in parallel.

When you trigger from the browser, since the user is triggering the action, until the action is done, your browser is busy processing the request and response.

I think as you are processing lot of objects you browser stops responding.

You can probably try dataviewloader, but it will still be showing the loading image until the task is done. But I am not sure if might kill the browser later due to the amount of data being processed.

You could also try to execute the microflow in the background, if you dont expect immediate response.

answered 2020-09-03

Nirmalkumar

Robert Price · Accepted Answer · 2020-09-03

As this is a long running process, you may be better getting this pushed into the background when the user starts the process, the same as the scheduled event does.

To do this, have a look at the Queue and ProcessQueue modules on the App Store. They allow you to push processes into the background so they don’t block the UI.