# EvalRotate in BFV without corresponding EvalKey **URL:** \ **Category:** Library Questions\ **Tags:** bugs\ **Created:** [February 29, 2024, 2:59am UTC](https://openfhe.discourse.group/t/evalrotate-in-bfv-without-corresponding-evalkey/1097 "2024-02-29T02:59:44Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Maokami](https://yyz1.discourse-cdn.com/flex031/user_avatar/openfhe.discourse.group/maokami/32/180_2.png) [@Maokami](https://openfhe.discourse.group/u/Maokami)\ **Post date:** [February 29, 2024, 2:59am UTC](https://openfhe.discourse.group/t/evalrotate-in-bfv-without-corresponding-evalkey/1097/1 "2024-02-29T02:59:44Z")
(continue from the issue [#675](https://github.com/openfheorg/openfhe-development/issues/675)) Hello, OpenFHE team! Thank you for taking the time to answer my query. What I wanted to point out is that the issue previously reported in [#362](https://github.com/openfheorg/openfhe-development/issues/362) still occurs in the BFV scheme. Specifically, calling `EvalRotate(ciphertext, index)` without first executing `EvalRotateKeyGen` for the index results in a `std::out_of_range` error. This behavior has been addressed for the BGV and CKKS schemes in #362, where it now throws an `openfhe_error`. While I understand that this scenario might not represent a valid use case, I thought it would be helpful to report this behavior, especially since #362 was labeled as a bug. Thank you very much for your attention to this matter! ---
**Author:** ![ypolyakov](https://yyz1.discourse-cdn.com/flex031/user_avatar/openfhe.discourse.group/ypolyakov/32/47_2.png) [@ypolyakov](https://openfhe.discourse.group/u/ypolyakov)\ **Post date:** [March 1, 2024, 4:02am UTC](https://openfhe.discourse.group/t/evalrotate-in-bfv-without-corresponding-evalkey/1097/2 "2024-03-01T04:02:57Z")
Thanks. We will look into this issue as soon as we are done with releasing v1.1.3, i.e., next week. Adding @dsuponitskiy-duality to this thread.