# Error Messages

<details>

<summary>Invalid ComponentId</summary>

I have seen the follwong message in two cases.

> Error: <https://api.boomi.com/api/rest/v1/abcfinancegmbh-5BZDOF/Component/7fb8b150-4784-4694-b365-db1e4db09f35> - http-400 (): ComponentId 7fb8b150-4784-4694-b365-db1e4db09f35 is invalid. Provide a valid componentId to complete this action.

<figure><img src="/files/SeZnEBbiPRYhKD9lrGBT" alt=""><figcaption></figcaption></figure>

#### Invalid child reference

When the mentioned ComponentId was a child component, the component XML was invalid. It happened after I imported a process from a different Account without importing a referenced profile. The profile was referenced in an Exception message. On the target system the references to that profile were still intact, whoever, the profile itself did not exist, because it was not imported.

To find this out, analyse the current component's XML and search for the ID that wasn't found.&#x20;

#### Invalid parent reference

I encountered the same message on a parent reference, too. This occurred on a process that was referenced as a *Data Quality Step* in DataHub.

<figure><img src="/files/3NIFcxMs1KFaYdp2W98n" alt=""><figcaption></figcaption></figure>

When checking the parent references it turned out, that the parent id is actually the DataHub's *UniverseId* (Model instance) on which the process is supposed to run.

Trying to open the component in the Boomi UI [https://platform.boomi.com/AtomSphere.html#build;accountId=abcfinancegmbh-5BZDOF;components={](https://platform.boomi.com/AtomSphere.html#build;accountId=abcfinancegmbh-5BZDOF;components=fd9ba676-f59f-4d92-b97a-8d70e24e9352,c458f559-e5e9-4a4b-88ad-d4dbb9002127;componentIdOnFocus=c458f559-e5e9-4a4b-88ad-d4dbb9002127)parentComponentID} lead to the following error:

<figure><img src="/files/fffc1hHp13M3jHypF7ld" alt=""><figcaption><p>IDTest is not a component. It is a DataHub Model!</p></figcaption></figure>

</details>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://boomi.markusschmidt.pro/power-tools/browser-tips.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.