It sounds like there seems to be a mixup in the team between branches in Xano and branches in Nordcraft.
When you merge a branch into main in Nordcraft, no other services are affected, e.g. Xano.
If new Nordcraft branch changes require database changes as well, you'll want to create a branch in Xano that matches up with the new front end changes.
When releasing, and publishing to main, it's important to publish the new branch in Xano at the same time.
There are ways to get around this to make development and publishing smoother, when using a service such as Contentful, for example, you can work on branches, and define the name of the branch to be used in the front end. When merging the front end changes, you can promote the Contentful development branch to the main branch, instead of merging in changes.
Ultimately it's a case of setting out a strategy for your team when these kinds of issues arise from many moving parts across different systems.
.jpeg/public)