![Microsoft Power Automate – Flow run history is missing from the Automation Center [MC1060388]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-fwstudio-33348-139319-1024x683.webp)
Message ID: MC1060388
Reports notified us that as of April 1, 2025, at 12:00 AM UTC, some flow run history may be missing from the Automation Center.
How does this affect me?
Our investigation determined that a code change made in a recent service update was incompatible with a backend service utilized to capture flow run historical data. We have created a hotfix to revert the code change. We expect the hotfix to be deployed by April 24, 2025, at 12:00 AM UTC.
What action do I need to take?
This message is for awareness and no action is required.
Please note, flows are running as expected, this issue is only impacting some flow run history.
Source: Microsoft
![Dynamics 365 Customer Service – Use shift bookings to assign conversations [MC1060311]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-everson-mayer-478307-1481309-150x150.webp)
![Microsoft Viva Pulse: Customize and display your internal usage guidelines for authors and responders [MC1060460]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-scottwebb-305821-150x150.webp)
The recent update regarding the missing flow run history in Microsoft Power Automate is certainly a topic worth discussing. As of April 1, 2025, at 12:00 AM UTC, some users may notice that their flow run history is not appearing in the Automation Center. While this may sound concerning, it’s important to note that flows are still running smoothly, and this issue only affects historical data capture.
For admins, this change presents a unique challenge. On one hand, it’s a reminder of the complexities involved in managing automation tools and the need for constant vigilance regarding updates and their impacts. The good news is that a hotfix is already in the works and is expected to be deployed by April 24, 2025. This proactive approach from Microsoft shows their commitment to maintaining the integrity of the platform.
On the user side, while some may feel a bit of nostalgia for their missing flow run history, the fact that flows continue to operate as expected should bring some comfort. It’s like losing your diary but still living your life to the fullest! Users can continue to rely on the functionality of their automations without disruption.
Overall, the impact of these changes might feel a bit like a bump in the road rather than a full-blown detour. Though it’s always a bit unsettling to see features temporarily go missing, the anticipated hotfix should restore normalcy soon enough.
I encourage everyone to share their thoughts and experiences regarding this update. What are your strategies for managing flow history, and how do you feel about the hotfix timeline? Let’s keep the conversation going! For more insights and ongoing discussions, check out other posts at mwpro.co.uk.