This is usually caused by issues with your n8n API access after a subscription change. First, try restarting your n8n instance to ensure the updated subscription details are applied. If the problem persists, verify your API key and connection details within the workflow, especially if you’re using any nodes that connect to external services.
Give that a shot