# ValueError: \`RLModule(config=\[RLModuleConfig\])\` has been deprecated- New API Stack

**URL:** <https://discuss.ray.io/t/valueerror-rlmodule-config-rlmoduleconfig-has-been-deprecated-new-api-stack/22104>\
**Category:** RLlib\
**Created:** [March 21, 2025, 8:31am UTC](https://discuss.ray.io/t/valueerror-rlmodule-config-rlmoduleconfig-has-been-deprecated-new-api-stack/22104 "2025-03-21T08:31:52Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![Daraan](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/daraan/32/7391_2.png) [@Daraan](https://discuss.ray.io/u/Daraan)\
**Post date:** [June 3, 2025, 1:16pm UTC](https://discuss.ray.io/t/valueerror-rlmodule-config-rlmoduleconfig-has-been-deprecated-new-api-stack/22104/17 "2025-06-03T13:16:25Z")

</div>

I only skimmed trough your topic. If it is the same warning message I am aware of you can safely ignore it. Currently there will _always_ be a deprecation warning for the very first `RLModuleConfig` config created.  
There still exists deprecated code that creates a `self.config = RLModuleConfig(...` from your new stack options for _backwards compatibility_, this instantiation throws the error

I wrote myself a snippet to run before my code to suppress this misleading warning

```python
from ray.rllib.utils.deprecation import logger as __deprecation_logger

# This suppresses a deprecation warning from RLModuleConfig
__old_level =__ deprecation_logger.getEffectiveLevel()
__deprecation_logger.setLevel(logging.ERROR)
RLModuleConfig()
__deprecation_logger.setLevel(__old_level)
del __deprecation_logger

```

Try if that hides the error. To be sure run it with a debugger and find the location, it could be a false postive and unrelated to your code.

---

_[View the full topic](https://discuss.ray.io/t/valueerror-rlmodule-config-rlmoduleconfig-has-been-deprecated-new-api-stack/22104)._