This happens when your bot is configured to use Datafeed 2.0 and has created a datafeed, but was not continuously running for some time so the datafeed became stale. The BDK will automatically re-create a new datafeed and begin listening on the new one after those log messages. As long as the bot is responding to events like commands, everything is working correctly. If you terminate the bot process and restart it, you will notice that the exception no longer occurs, since your previous run already created a new datafeed. The Python BDK as of version 2.3.0 defaults to using Datafeed 2.0, which does not persist a `datafeed.id` file to disk. Instead, all datafeeds are stored in the Symphony Cloud to improve bot resilience. As for presence, your bot should appear online as soon as your bot process starts up and the datafeed loop begins.

This happens when your bot is configured to use Datafeed 2.0 and has created a datafeed, but was not continuously running for some time so the datafeed became stale. The BDK should automatically re-create a new datafeed and begin listening on the new one after those log messages. Can you confirm if the bot is responding to events like commands? If it does not, please provide the version of the Python BDK you are using and the contents of your configuration file.

It happens when your bot is configured to use Datafeed 2.0 and has created a datafeed, but was not continuously running for some time so the datafeed became stale. The BDK should automatically re-create a new datafeed and begin listening on the new one after those log messages. Can you confirm if the bot is responding to events like commands? If it does not, please provide the version of the Python BDK you are using and the contents of your configuration file.