> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/getintio-platform/handling-syncs-for-deleted-items.md).
# Handling Syncs for Deleted Items
When working across different platforms or systems, it’s essential to understand the limitations related to data synchronization. One critical area where limitations exist is the synchronization of deleted items. In this article, we’ll explore the current limitations regarding deletion sync and provide a recommended workaround.
### Current Limitation
The issue arises when an item (such as an issue, task, or record) is deleted on one platform. Unfortunately, this deletion does not automatically trigger a corresponding deletion on the other platform. In other words, if you delete an issue in Platform A, it won’t be automatically removed from Platform B.
### Recommended Workaround
To address this limitation, consider implementing the following workaround:
1. **Create a “Deleted” Status or Label:**
* Go to your app instance and create a **custom status** or **label** specifically for deleted items in your workflow.
* Apply this status or label to any item you want to mark as **deleted.**
Label created to identify Deleted issues. We’re using a Jira instance as an example
Custom status created for Deleted issues
{% hint style="info" %}
If you want an in-depth guide on how to create custom fields, please visit our article here: [How to create a custom field](https://docs.getint.io/guides/integration-synchronization/how-to-create-a-custom-field-in-all-support-software).
{% endhint %}
2. **Manual Cleanup:**
* Regularly review items with the **Deleted** status or label.
* Manually erase these items from the other platform as needed.
Please note that syncing deleted items is not supported, and there are no current plans to implement it. While this workaround adds an extra step, it helps mitigate the limitation effectively.
---
# 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://docs.getint.io/getintio-platform/handling-syncs-for-deleted-items.md?ask=&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.
.png?alt=media&token=2b06d240-5bc2-41c4-bee2-9c9a0f5688d5)
.png?alt=media&token=b18b11c2-d3cc-42c3-8965-ed492e653bdc)
