Thanks for response! Actually talking to our development team, we realized that there were more than one instance of N8N working without configuration. We turned them off and the problem was actually solved.
That action generated another problem as described in this new post:
As the solution in the post, the roll back to version 0.209.0 solved the new bug.