@aaroh_bits
As mentioned @ScottShearer Power Automate are much more powerful than Designer workflows. But one thing we need to understand that Power Automate is Platform Independent. Unlike SharePoint Designer workflow which were tightly integrated to SharePoint Power Automate can Connect between various data-sources(https://flow.microsoft.com/en-us/connectors/)
- >> Power Automate does not fit the all the requirements such as 30 day run limit for Power Automate.
With reference to the above Scotts answer is right on the money. If you contact Microsoft Support with above question they will point you to https://docs.microsoft.com/en-us/power-automate/limits-and-config#run-duration-and-retention with a reply below:
As long as the Flow is active (turned on) and the connections used within the Flow are still valid, the Flow should be working as expected.
A connection being valid means that the access token is not expired. The access token is acquired during logging process (when you enter your credentials to create a connection) or during a Flow run when the third party service provides a mechanism to automatically extend the access token (usually via refresh token).
For example, if you have a SP online connection and it’s not been used in any Flow for 90 days, the next the Flow that contains that connection runs, we probably will receive an authentication error.
From Flow perspective, it does not have anything to do with the expiration period of the services that it’s trying to connect to. For SharePoint it’s 90 days but for Gmail connection, it might be different. Thus, I would suggest to check the token lifetimes of the third party services before deploying any Flow interacting with them.
To sum it up, the validity of a Flow which is not being triggered will depend on the lifetime of the connections it is using. For some services, you can extend the token lifetimes but then there will be a tradeoff between security and accessibility. Otherwise, you just need to make sure the connection is refreshed within its lifetime (by log out and log in, or run the Flow once in a while).
The above is copied from https://powerusers.microsoft.com/t5/Building-Flows/Flow-30-days-limit/td-p/446229
- >>Power Automate does not have workflow task center which is a high impact on client's operational for each task and monitoring.
We have been using Planner(https://tasks.office.com/ ) to instead of workflow task, you might want to have a look at https://sharepointmaven.com/microsoft-planner-vs-tasks-web-part/#:~:text=Microsoft%20Planner%20has%2....
- >> Power Automate does have impersonation which workflow 2010 has it.
You should consider Manage run-only users https://www.chakkaradeep.com/2018/05/22/managing-owners-and-users-for-your-sharepoint-list-flows/#:~... '
or decouple your Power Automate solution (Parent child Flow), which will help you manage this scenario, have a look at my article at https://clavinfernandes.wordpress.com/2020/09/04/decouple-the-flow-from-the-power-app-to-prevent-end...
- >>No concept Reusable Workflow in Power Automate
There is no concept of a reusable workflow, but you can easily, Export and import Power Automate, You can also have a look at http://johnliu.net/blog/2019/3/one-flow-to-handle-them-all-how-to-subscribe-to-multiple-sharepoint-l...
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
