Struggling with the new Run Dashboard
Planned
Am I missing something or did the ability to see run history actually get removed from the UI?
In the "old" UI you could see the stats for the individual "bubbles". I've clicked all over and can't find a way to show the detail. What am I missing? I can't imagine this critical information would have been removed from the UI, was it?
Side note: If it's going to present two exports as two runs, maybe add an export column or a tooltip or something so you can tell which is which? Just a thought, maybe there is an even better or simpler way.
-
Official comment
Hello Steve,
I wanted to let you know with the latest release, you will have the option to drill down in the specific run and view statistics about the run in the Run history Tab.
You can read more about this new change in this Article
Thanks for this valuable feedback, it proves immensely helpful in making our Product better.
Regards,
Akhilesh Goyal -
Thank you for providing your feedback on the new run console.
The "Run history" tab shows the summary result of success count and ignored count and error count and the "Run console" tab shows the result for each step for the most recent flow run.
To view past result stats for each step, you can use the flow dashboard that charts the result as a time-series line chart. See this kb for detail: https://docs.celigo.com/hc/en-us/articles/360048814732#graphs
Thanks
0 -
Viliandy,
Thank you for your reply. I understand that the Run Console is only the most recent run and I'm getting used to that view more and more. I don't understand why the Run History would not have the ability to drill down and see the individual components of a run. That was a feature that I used often and am missing. The reports and graphs are useful as an overview or to see trends, but they don't meet my needs to see what happened (in detail) 2, 3 or 5 runs ago.
Hopefully adding drill down capabilities will be considered in the future, until then I'll try to figure out another technique.
0 -
Why would you need to see what happened 2,3, or x runs ago? How does the information help you with monitoring or resolving errors? Please let me know if you'd find it easier to discuss in person and I'll set up a meeting.
Thanks
0 -
I would want to see what happened in previous runs as part of troubleshooting and development.
How many records did the lookup skip before we changed the setting to XYZ?"
I would check this by reviewing the detailed steps for that run - I don't think this is possible in the new version, is it?
or...
The NetSuite script threw a bunch of errors, what did Celigo send?"
In which case I'd look back at previous runs to access the errors (if any) and possibly look at retry data.
Or...
None of the records were copied to the S3 backup folder but the flow ran because Shopify was updated, what happened?
You get the idea I hope.
Unless I'm missing something, the new version has removed data that us "developers" found useful and relied on.
0 -
We are working through some details internally about adding back the statistics (number of success, ignored, errors, auto-resolved) per flow run in the flow run history view.
One option that you may explore is to run flow events report (read here about how to run this report) which lists all records processed (success, ignored, errored, resolved) when the flow runs at specific time window. Each record is uniquely identified by its trace key (read here for setting trace key).
Please let us know if you are interested in providing us feedback for future iterations of the run history functionality.
Thanks
0 -
Although this is a 2yr old thread, this is still important. I am using the Netsuite - Shopify integration app, and working on the Shopify Order to NS Sales Order flow. With any successful run i cannot see even the ID of the json object that passed though celigo. I am trying to debug an issue where i want to know if an order update was triggered or sent to celigo, and i have no way of knowing which order did or did not get processed, unless it has an error. This seems like it is basic logging functionality. I could log data to an external service but that would take a lot of effort.
0 -
Jolyon Blazey Thank you for sharing the use case and the requirement. We have this feature (i.e. access to success and ignored records) in our backlog and will prioritise it.
0 -
If all you need to see is the primary id (i.e. traceKey) of the records being processed, then we support this via our "Flow events" reports. See the following screenshot for context. Hope this helps!
0
Please sign in to leave a comment.
Comments
9 comments