A team migrates a Node.js handler to Python but leaves the handler string pointing at the old export name, causing runtime import errors. What must be aligned?

The bouncer checks both the language on the invitation and the door marked on the map. After moving from Node to Python, point runtime and handler at the new module.function entrypoint—or Lambda keeps looking for an export that no longer exists. IAM, memory, and log group renames won't fix a wrong handler string.