Repository navigation
Releases
Environment Analytics 1.2.0
Import it over any earlier version the same way; it upgrades the app in place.
Added
- Suspended flows, in environment health, quoting Power Automate's own reason where it gave one.
- Flows that have gone quiet, in environment health. When a trigger's connection expires, the flow doesn't fail: it simply stops running, so no failed run is ever recorded. The app learns when each regular flow normally runs, hour by hour across the week, and flags it once it has missed about three runs it would normally have made. Nights and weekends don't count against business-hours flows.
- Filters on the Flows page for suspended flows and flows that have gone quiet, and an explanation on the flow's own page when it has been flagged.
Only flows with at least five runs on five separate days in the selected period are judged for going quiet. A flow that runs once a day needs two or three missed runs before its silence is flagged, so a single quiet day, or a bank holiday, doesn't raise a false alarm.
Install
Solutions > Import solution in make.powerapps.com, choose the zip, import. Take the managed zip unless you intend to change the app. Code apps must be enabled on the environment, and users need Power Apps Premium. Full steps are in the README; every change is in the changelog.
Environment Analytics 1.1.1
A fix release. Import it over 1.1.0 the same way; it upgrades the app in place.
Fixed
- Flow run durations were a thousand times too long. Dataverse stores a run's duration in milliseconds, and the app read it as seconds, so every duration it showed was inflated.
- Run time is now the median, not the average. A few runs left waiting days on an approval made the average meaningless. The dashboard and each flow now show a typical duration (median), with a count of runs that waited over a day. The optimisation scatter and slowest-flows chart use each flow's median; dot size is still total time spent.
- Durations over a day read as days and hours.
Install
Same as before: Solutions > Import solution in make.powerapps.com, choose the zip, import. Take the managed zip unless you intend to change the app. Code apps must be enabled on the environment, and users need Power Apps Premium. Full steps are in the README.
Environment Analytics 1.1.0
Import this into any Power Platform environment; there is nothing to build.
Which file
- Managed (
..._managed.zip): for anyone installing the app to use it. Recommended. - Unmanaged (
....zip): only if you intend to change the app in that environment.
Install
- In make.powerapps.com, pick the environment, then Solutions > Import solution.
- Choose the zip and import.
- Open Environment Analytics from Apps.
Before it works
- Code apps must be enabled on the environment: Power Platform admin center > the environment > Settings > Product > Features > Enable code apps.
- Licensing: people who open the app need Power Apps Premium.
- Security role: System Administrator is the only built-in role Microsoft documents as reading every table the app uses. With a narrower role, people see only what their role can read, and the affected sections say so rather than showing zero. Agent conversation figures also need Bot Transcript Viewer.
The app is read-only. It queries the system tables Dataverse already keeps and writes nothing back.
What's in this version
- Environment health: fourteen checks, ranked, each linking to the records behind it
- Light, dark and system themes
- WCAG 2.2 AA contrast, keyboard operation, and a data table behind every chart
- Charts built on LayerChart
Not yet verified: importing into a different tenant from the one it was built in. If you hit a problem, please open an issue.