While trying to view the reports I faced this issue.
Honestly, I don’t know the exact steps for this error, but it is definitely not looking good from user POV.
Maybe team can keep a track of this.
2 Likes
Thank you Akshay, I have forwarded this report to our team for further investigation.
clear cache and cookies and restart testops. let us know
1 Like
this looks like an internal application error on the TestOps side, not something caused by user actions
please check the application error logs in splunk or other moniitoring tool and request your devs to handle these errors gracefully since these are reactjs errors not from katalon side
I tried that already and even a simple reload did the trick for me.
But the point is why?
Why as a user should I see this error?
These needs to be handled gracefully.
Also this scenario is not happening always. I encountered only once, but Katalon should handle this.
If anytime I’m able re-create this issue I’ll note down the exact steps.
1 Like
Dear Akshay,
I created a request and I was just notified that the issue had already been fixed in app. Can you retry it again.
Let me know if this is still an issue
Bella
Did Katalon do anything to fix the @akshay_sartabe’s issue? If yes, then at which version of which product Katalon implemented the fix?
Or do you just mean that you could not reproduce the issue on your side?
this is a UI rendering issue as mentioned in your original screenshot
what the fix provided to address OP’s issue. can we get the release notes on the fixed deployed?
does this occur only in tesops? not on local machine/
Dear Mr Kazu, we will get back to you on this once I have a firm answer. Thank you for your patience.
Hi @kazurayam @akshay_sartabe The original issue raised by @akshay_sartabe has been reproduced and fixed in an ad-hoc hot fix yesterday. And the issue only happened in TestOps cloud, not in OP version. Kindly help verify this. Thanks, guy.
thanks for the updates 
Great.. Atleast now I can get my mind of this topic.
Thanks for the update. Good to hear that it was fixed in hot fix.
You guys should also also include in the Release Notes.
1 Like