In Horizon Rules today, execution logs are completely erased after a certain time period. I don’t just mean the actual execution files to see what records ran, I mean the fact that the rule had any execution history at all. After a certain time it’s just blank.
Example:
This gets confusing when you look at the Last Run Status in the Rules List UI and you see something like “Success” or “Failure”, but there’s no execution history.
Same Rule:
How has it run successfully but there are no logs? Answer - they get completely erased.
Maybe it’s a huge drain on infra to even keep the visual logs around, but as an admin, I still need *some* historic information about each rule in the execution history.
Here’s what I would like to see in the execution logs as a cumulative summary that shouldn’t take up much processing:
| Run Status | Success | Partial Success | Failure |
| Cumulative Count | 54 | 33 | 0 |
| Last Run Date | 12/25/2025 | 01/31/2024 | N/A |
This gives an admin the immediate information that the rule has in fact run at some point, what the status of the last run was, and how many times the rule has run in general. This is basically just a cumulative counter and a “last date stamp” that doesn’t need constant recalculation and should be cheap and easy to do compared to keeping years of actual log data.
This would also be useful for Data Designs, JO Queries, or other similar jobs (like Rule Chains) that have some type of execution history.