> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/multi-language-and-text-tagging-support/resolve-node-level-translation-conflicts.md).

# Resolve Node-level Translation Conflicts

When you copy and paste a node from one logicnet to another and then make a change to the caption in that node the system displays a note telling you about the conflict between the original node and the copied version. For example, if you create a node that asks a user to identify a type of car you can copy and paste that node into another logicnet. If you then change the questions in the copied version of the node to make the word "car" into "cars" the system displays the following message.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-1ff84cbd0a86193a8b4084a0c3486ca5abb5b54c%2Fabf45330-3b38-4086-a296-15c77f64f182.png?alt=media)

The system gives you the option to make the update in both nodes. Click ***save*** to have the system keep the same translation key for both nodes. Or click ***new key*** to make the change in the copied node only. The system creates a new translation key for the copied node.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/multi-language-and-text-tagging-support/resolve-node-level-translation-conflicts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.