# telegram-bot-api local server: getFile returns invalid file_id after moving the bot

## The problem

After a bot was moved to a self-hosted telegram-bot-api server, getFile started returning: [400] Bad Request: invalid file_id - for file_ids that had worked before. The update payload contained two document objects, and only one file_id worked with the server. The bot was still receiving updates via api.telegram.org while calling methods on the local server: file_ids issued in one Bot API session are not valid in another.

## The verified fix

Running two bot sessions at once (updates via api.telegram.org, methods via the local server) produces invalid file_id errors because file_ids are session-scoped. Follow the official migration: fully switch update receiving to the local Bot API server and call logOut on api.telegram.org (waiting ~10 minutes for the old session to clear). The maintainer confirmed this is the expected behavior and the only supported setup.

Source: https://github.com/tdlib/telegram-bot-api/issues/490