@MarcLasserre_GCS  

I do understand on the maintenance overhead but

1. Shouldn't the warning be introduced when its exceeding 15 steps or  like how Obj-Save (Write-Now) issues a warning specific to the method usage, rather than introducing "a moderate warning of reduce activities always" , or 2. For example you will have to use Queue-For-Processing method, but there isn't an alternative (Excluding flow shape)  but to use an activity to trigger a background API call from UI by the user to fetch an information and besides even the queue-processor rule also needs an activity. (Just a random example). 3. It also impacts Guardrail of an application when being used for right reasons as well at times.

Are there any other issues like for example compilation of java in activities takes time due to "ABC" reasons and impacts performance so reduce its usage or like security related issues due to custom java and so on. Upon checking further I came across that the link I was referring to in the question, details the pros and cons associated with activities rather than indicating maintenance issue only. Hence the query to look for some viable document or information regarding this warning and misconception around activities.  I highly appreciate , if you could message me the contents of that link in a pdf for example or provide me with a link where appropriate information is given. Thanks