The issue where desktop flows triggered from cloud flows in Power Automate run successfully but show no actions in the run details is a known problem affecting versions 2.59.154.25213 and 2.59.163.25230. This symptom—empty or missing action logs despite successful execution—is linked to how action logs are recorded and retrieved.
Key points and suggestions:
1. **Action Log Version V1 vs V2**
- V1 stores logs in the AdditionalContext field of the FlowSession entity; V2 logs are stored in the FlowLogs table with improved management.
- Enabling V2 was intended to fix similar issues, but as updated, it did not resolve your case, indicating a deeper or different root cause.
2. **Known Community and Microsoft Issues**
- Several users have reported missing run details for desktop flows in these versions, often linked to telemetry or logging service disruptions or bugs in the desktop flow agent.
- Microsoft has acknowledged related issues in some release notes and is working on fixes in newer releases.
3. **Recommended Actions:**
- **Update to Latest Versions:** Check if there are newer desktop flow client and agent updates beyond the reported versions; bugs affecting logging may have been fixed.
- **Clear Cache/Restart Desktop Agent:** Sometimes stale cache or agent glitches cause log retrieval problems. Restarting or reinstalling the desktop flow agent may help.
- **Review Power Platform Admin Center Logs:** Admin insights may show errors or warnings associated with flow runs that don’t appear in the run details UI.
- **Raise a Microsoft Support Ticket:** Provide detailed logs and environment info for assisted troubleshooting since this issue can be complex to debug independently.
- **Community Forums & Updates:** Monitor official Power Automate forums and release notes for known issues and patches.
4. **Interim Workaround:**
- Use alternative monitoring, such as tracking output variables via cloud flow steps post-desktop flow runs or external logs to validate execution until logging issues resolve fully.
In summary, this is a recognized problem with certain Power Automate desktop flow versions, and while switching log versions was a good attempt, the root cause may require updates or vendor support. Upgrading, agent restarts, and Microsoft support engagement are advised steps to mitigate and resolve this issue.
