# Suggestions for Better Actions Reporting

**URL:** <https://community.pickaxe.co/t/suggestions-for-better-actions-reporting/8895>\
**Category:** General\
**Created:** [October 2, 2026, 1:20am UTC](https://community.pickaxe.co/t/suggestions-for-better-actions-reporting/8895 "2026-10-02T01:20:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenlyle](https://avatars.discourse-cdn.com/v4/letter/k/ac8455/32.png) [@kenlyle](https://community.pickaxe.co/u/kenlyle)\
**Post date:** [October 2, 2026, 1:20am UTC](https://community.pickaxe.co/t/suggestions-for-better-actions-reporting/8895/1 "2026-10-02T01:20:12Z")

</div>

It’s difficult to clean up Actions efficiently with the current minimal data provided. Suggestions:

Usage

- Runs in the last 24 hours, 7 days, and 30 days
- Last run time
- A sparkline of runs per day

Health

- Success and error rate, with the last error message
- Latency (median and 95th percentile)
- Timeouts

Where it’s used

- Every Pickaxe the action is attached to, each with its own last-run time
- Dead or unattached actions are flagged

Config

- Required variables, and for each connection whether a value is set
- Never the secret itself, but “set / empty / changed on date X”

Lifecycle

- Created, last edited, last deployed, owner
- A version history with diff

Cost

- Credits or compute used
- Who is being charged

Actions on it

- Edit, duplicate, export, delete
- A warning that lists the affected Pickaxes before deleting