Solved
Forum Discussion
zacdavidson30
6 years agoNew Contributor
We are encountering this issue as well; however, we re-installed ReadyAPI Version 2.3.0 and everything works as expected. I think there may be a bug in ReadyAPI 2.4.0.
Hi maged_ahmed,
Thank you for sharing the w/a with the Community! The described issue is the known one in 2.4.0. It's fixed in the maintanence build of version 2.4.0 and in version 2.5.0.
We are encountering this issue as well; however, we re-installed ReadyAPI Version 2.3.0 and everything works as expected. I think there may be a bug in ReadyAPI 2.4.0.