Hi,
I’ve create a REFramework process who has many work with many transactions (> 28.000).
I’ve separate Dispatcher and Performer.
My idea is that Dispatcher could create a pack of transaction for a day (ie 500) and the Performer run long hours ago each day.
Is it a good practice to let’s run a process 8-10 or more hours in one shot or is it better to cut the execution in x run with triggers ? For me, the second solution is more complex because it’s not easy to be sure the prev process is ended.
So, is it for you a bad practices to let a process (based on REFramework) to run 8-10 or more hours ?
Not at all. You are just utilizing the full potential of your license.
We have multiple processes which runs almost 23 hours and those are running completely fine.
If you don’t have any other issues, you can go for it.
Hi @SA64
If you are using performer and dispatcher using queue, it is fine if performer run for long hours.
Make sure that exceptions are handled and logged properly.
Also consider that other jobs will be in pending state if this bot runs for long hours, you should also consider about the other bots and availability of free robots.
In case of dispatcher if you are uploading 500 items each time you can trigger your dispatcher at end of performer so that dispatcher will add next 500 items to queue and your process keep running.