Hi @sudhakar_Y !
For the best practices part from your question:
Try these best practices:-
1. Have you tried implementing logging in your flow?
- If not, try creating a text file or .html file (save as from text file).
- Use html tags like 'p' (paragraph tag) etc.
- Also add date and time to see when your flow has executed an action. Example like given below:

There are many ways to do logging. There are as follows:
1. Store logs into a csv file
- Refer to this video: https://youtu.be/QjrxLPg_TdI?t=3510 to get any idea about it.
2. Store logs into text/html file
- You can also store in text/html file. Here is an example of how it shows in html:

In this I used html, so you need to use html tags like <p>, <h1> (heading tags). I also keep the time recorded when it finished that action.
Like this:

These are the actions I use for logging into html files. Make sure to use .html extension to save it as html doc.
3. Store logs into excel file
This is another I currently use. Take a look of how it shows:

I keep detailed logs like this in excel. It shows if a particular file name is a success or not. It even shows how long a flow has taken to execute calculated by total time taken (end time - start time). And errors will be stored in one column. So like if no errors are found, its a success, else failure.
2. Have you tried implementing error handling in your flow?
- If not, try using the 'On-block error' action for a block of actions. This will immediately get the error within that block of actions. Use a variable to store that error.
- You can also use 'Get last error' action which creates a variable to store the last error you got in your flow and then add this to your log file.
- Use the 'Retry' policy for a particular action where the error occurs.
- Use 'Continue flow run' in the actions you think are giving an error. Repeat action, Go to next action or Go to label (will be usable if you created a label in your flow). Example like given below:

- When logging errors, use a 'style' attribute in your tags with hex code or color red indicating an error has occurred.
There are many more. I have attached a zip file containing the best practices in more detail and for many more use cases.
Also here is one really awesome YouTube link by the infamous, Anders Jensen: Power Automate Desktop: Best Practices for Advanced Users