Identifying the Null 'id': Resolving Database Migration Challenges and Table Dependencies

[GuilhermeTrivilin]

The credentials issue has been resolved, however, when I try to click on “Execute Node,” I receive an error message stating that the “id” cannot be null. But it does not specify which table is receiving the null “id”.

Please note that I’m conducting a database migration, here are all the tables that I am migrating from the old to the new database:

• auth_identity
• auth_provider_sync_history
• credentials_entity
• event_destinations
• execution_metadata
• installed_nodes
• installed_packages
• migrations
• role
• settings
• tag_entity
• user
• shared_credentials
• variables
• webhook_entity
• workflow_entity
• shared_workflow
• workflow_statistics
• workflows_tags

Information on your n8n setup

• n8n version: latest
• Database (default: SQLite): PotsgreSQL
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Amazon Linux

[Jon]

Hey @GuilhermeTrivilin,

I might have missed an issue but… How are you doing your migration and where does the error appear?

[GuilhermeTrivilin]

Apologies for the poor contextualization. This post was meant to be written as a response to another, but I created a new topic to separate the subjects.

Context: I am performing a database migration for my N8N application. Instead of using a PostgreSQL database on AWS RDS, I have set up a new database on an EC2 instance to store N8N data. Now, I am migrating data from the old database to the new one.

Everything is functioning well, and all the data is present as expected. However, when attempting to execute the workflow, I receive an error stating that the ID field cannot be null, but it does not specify the table or provide any additional information.

[Jon]

Hey @GuilhermeTrivilin,

It might not be an issue with the database, if you can show where the error is in a screenshot we might be able to work it out.