> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/tutorials/delete-assets-that-are-missing-from-source.md).

# Delete assets that are missing from source

As a result of import or synchronization operations, assets that were present in your Collibra environment but are no longer available in the external system may have their status changed to **Missing from source** instead of being permanently deleted. After a review of those assets you may want to remove them from Collibra. You can use the **Delete missing assets** workflow to delete any assets from a selected domain that have the **Missing from source** status.

{% hint style="success" %}
Download the [**Delete missing assets**](https://cdn.collibra.com/developer/Delete%20missing%20assets-bar.zip) workflow.
{% endhint %}

{% hint style="success" %}
You can adjust the workflow to target any other status by updating the **statusId** process variable.
{% endhint %}

## Configuration

After you have uploaded the workflow to your environment, access the workflow configuration via <img src="https://2912049260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8DYDBo6jzvQ73H6CZj6k%2Fuploads%2Fgit-blob-75245abf5c50ddf56f1d2d727ccaacf757d11145%2Fcogwheel-large%402x.png?alt=media" alt="" data-size="line"> **Settings** → **Workflows** → **Definitions** → **Delete Missing Assets**.

![](https://2912049260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8DYDBo6jzvQ73H6CZj6k%2Fuploads%2Fgit-blob-a0f476d80fdc536de49eafb3d62e7aca5597f981%2Fdocs_workflows-delete-missing-assets-configuration.png?alt=media\&token=dd15f6a4-e4dc-4cd6-abdc-b3e4dbd5ffb0)

The workflow is meant to run at the community level. You must change the scope of the workflow to apply to **Community**.

Additionally, you may want to change the description, the start label or to allow only specific roles to be able to start this workflow.

## Walk-through

After you have enabled the workflow, go to a community containing domains with assets that are missing from source. To start the workflow, click **Actions** → **Delete Missing Assets**.

<img src="https://2912049260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8DYDBo6jzvQ73H6CZj6k%2Fuploads%2Fgit-blob-312dc5c60419fe2bdc1775db07f0618b7a44c12a%2Fdocs_workflows-delete-missing-assets-label.png?alt=media" alt="" width="563">

You must select one or more domains from the current community and acknowledge that deleting those assets is an irreversible process before you can click the **Delete missing assets** button to permanently delete those assets.

{% hint style="warning" %}
Depending on the number of assets that have the **Missing from source** status, the workflow may take some time and computing resources to complete.
{% endhint %}

## Additional resources

* Download the [Delete missing assets-bar.zip](https://cdn.collibra.com/developer/Delete%20missing%20assets-bar.zip) workflow to publish in Collibra or edit in the Workflow Designer
* Read the [Workflow Designer documentation](/workflows/workflows-at-collibra.md).
* Read the [Introduction to builders](/tutorials/introduction-to-builders.md) tutorial.


---

# 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://developer.collibra.com/tutorials/delete-assets-that-are-missing-from-source.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.
