The node is not valid as its type (n8n-nodes-base.httpRequest) is unknown

[GlitchWitch]

Describe the bug
After upgrading to [email protected] and creating new HTTP nodes with credentials, those nodes appear broken and display an error after saving and logging out.

To Reproduce
Steps to reproduce the behaviour:

1. Upgrade from 0.177.0 to 0.178.0
2. Add an HTTP node with an existing credential type (in this case a slack API token)
3. Save and test the workflow, confirm it works
4. Logout, then login and reopen the workflow
5. Note that HTTP nodes now show a question mark as well as an error.

The node is not valid as its type (n8n-nodes-base.httpRequest) is unknown

Expected behaviour
The HTTP node should not break after being setup.

Environment (please complete the following information):

• OS: Ubuntu 20.04
• n8n Version: 0.178.0
• Database system: SQLite
• Operation mode: own

Additional context
Despite the error the node continues to function as it did before.

[ivov]

Thank you for your report.

Can you please share a simplified version of the workflow that triggers this behavior?

I could not reproduce following your steps.

[GlitchWitch]

@ivov, this seems fixed as of [email protected] #3371