Forum Discussion
richie
Community Hero
Hey mithunbhat,
No....it'a definitely a defect....i've had a number of similar issues in versions 2.3 and 2.4 and 2.5.
Can you please raise a support ticket with Smartbear? They'll want to know about this...what version are you running?
Cheers,
Rich
No....it'a definitely a defect....i've had a number of similar issues in versions 2.3 and 2.4 and 2.5.
Can you please raise a support ticket with Smartbear? They'll want to know about this...what version are you running?
Cheers,
Rich
mithunbhat
6 years agoOccasional Contributor
I am running version 2.8.0
- TanyaYatskovska6 years agoSmartBear Alumni (Retired)
Hi mithunbhat,
I see your support case regarding this issue. The Support Team didn't reproduce the issue in their test lab. Could you please follow their recommendations to check if this helps?
- Olga_T6 years agoSmartBear Alumni (Retired)
Hi mithunbhat,
It would be great if you could update us on your progress here regarding that support ticket. Was the investigation successful?
- jbattaglia5 years agoOccasional Contributor
I am also facing this issue.
What are the steps that your support team recommends to resolve?
thanks
- richie5 years agoCommunity Hero
Hi jbattaglia,
I don't know whether the previous support case has been closed or not.
I did see this behaviour in earlier versions but its been quite a while.
What version of readyapi! are you using?
You can try submitting a new call with smartbear.
Nice one,
Rich
Related Content
- 6 years ago
- 8 years ago
Recent Discussions
- 18 days ago