From a troubleshooting perspective, similar to the Workflow automator execution logs, it would be nice to have some sort of supervisor rule execution log that shows all tickets a supervisor was run on. This would allow us to see if things are triggering more/as/less often than desired for a specific rule more proactively after implementation into production rather than having to wait for a user to complain about something not happening when desired OR something happens every hour (and being able to isolate if it is a specific ticket issue, or a global config issue).
New Idea
Supervisor execution logs
Thanks for sharing this idea! Detailed supervisor execution logs would actually solve a lot of the visibility gaps teams face today. Right now, it’s hard to understand what rules were triggered, when they ran, and how often they executed — especially when troubleshooting ticket behavior after deployment.
Having something similar to the Workflow Automator execution logs would make it much easier to track unexpected triggers, validate rule changes, and identify issues before end-users even notice them. Even a simple timeline or action history would help teams stay proactive instead of reactive.
Totally unrelated, but I was recently reading about a Blowout Taper Haircut and it made me laugh how much “clear structure” matters everywhere — in hair layers and in execution logs. 😄 Clear logs = cleaner ops.
Hope this idea gets picked up in a future update — it would add a lot of value for many users.
Join the Community
Already have an account? Login.
Sign in to the Community
No account yet? Create an account.
Social Login
Login for Freshworks Employees Login with LinkedInor sign up below
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.