Re-run query when a graphed action's steps changes
Bug description
When graphing an action, then updating its definition and returning to graph the same event, the query doesn't get re-run automatically. This can make the user think they inaccurately redefined the event, when they just need to click the Refresh button.

Expected behavior
If any events in the graph have been redefined since the query was run, re-run it.
How to reproduce
- Graph an action in Trends
- Click Events and change its definition
- Re-visit Trends and graph the event
Graph will show the query has not been run since the event was just redefined
Not so sure about this one. We don't rerun the query if it's cached (for performance and UX reasons), that's why the label appears. Maybe the label needs to be a bit more obvious?
Right, but point is, if you change the definition and return, it should probably bust the cache since the data will then be stale, no?
Well maybe what happened is that the definition you returned to was cached anyways. Did the graph looked awfully wrong or just not updated?
As we figured out during the planning, the issue mixed up "action" and "event". Busting the cache for an insight that shows the cache seems hard, but doing it on the frontend should be easy (get the cached results, see that the action is not the same anymore, refetch)
This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.
This issue was closed due to lack of activity. Feel free to reopen if it's still relevant.