regarding process model?

You can cancel this process to improve site performance. What is the use case for creating a process that can loop indefinitely?

I agree with Colton, Why are you implementing this kind of loop? can you tell us about your use case?

Is not good idea having just 1 process running and never stopping because that way you cannot kill it just like that.
Maybe you really need something scheduled every 1,2, 10 minutes? this you can achieve with a timer event, with time recurrence every X minutes, then you don't really need a loop. Every time it is executed it will create a new instance, that way you can even monitor easily each execution.

But please tell us about your use case. maybe we can suggest another ways to achieve the same.

Jose

Hi Aswini its obvious, when you loop the process for infinite time, will slow down your environment.


The best way to perform loop (but not infinite) is, during non business hours, let's say 11 pm till 5 am (varies) so, during this time it should process batch of data, and remaining will be picked up during next batch processing.

I don't think, in any way, you will need to perform infinite loop.

It will be good, if you can elaborate about your use case scenario, to understand the best possible way for your case.

As the process constantly loops and never terminates it will consume more and more memory over time. Reviewing your use case against a short lived process design that can be archived, or deleted, and balanced across engines will better utilize and release system resources.

As others have mentioned, if you can provide additional context on your use case we may be able to help you brainstorm a better design. Constantly looping through an open process 24x7 will always have issues given enough time.

I would suggest reviewing the playbook article on Creating Memory Efficient Models to help provide direction on your design.

community.appian.com/.../creating-memory-efficient-models