Why Is the OpenRouter Node Unrecognized in Live n8n Executions?

Based on the error message, it appears that the production execution environment isn’t recognizing the OpenRouter node type (internally registered as lmChatOpenRouter). Here are a few things to check:

1. Node Registration:
   Ensure that the custom or additional node is properly installed and registered in your production instance. While testing in the editor might load the latest code, the scheduled execution process could be running an older or different version that lacks support for this node.

2. Version Consistency:
   Verify that both your editor (test) and your execution process are running the same n8n version and have the updated node packages. If you recently added support for the OpenRouter node, confirm that this change is deployed to your live environment.

3. Deployment Process:
   If you’re self-hosted via Docker or another method (like Railway), make sure that your build or deployment includes the installation of the node’s package or any custom nodes configuration. Sometimes a production build does not pull in the latest changes until you update the image or clear any node cache.

4. Custom Node Setup:
   If this is a custom or community node, double-check the instructions for installing it. You might need to adjust settings or install an additional package so that the node is available during live executions.

In summary, the error is generally due to the production environment not recognizing the new node type—likely because of deployment, version, or configuration differences. Verifying and synchronizing your environments should help resolve the issue.