> 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/workflows/filtering-items-for-integration-in-getint/troubleshooting-sync-issues-unmet-filter-conditions.md).
# Troubleshooting Sync Issues: Unmet Filter Conditions
## Introduction
Filters allow you to control which items Getint synchronizes between connected platforms. When an item does not meet the configured filter criteria, Getint will skip the synchronization to ensure that only relevant data is processed.
This article explains how to identify items that failed to sync due to filter conditions, review the filter configuration, and resync affected items after making corrections.
***
### Identifying Items Affected by Filters
1. Open your integration and navigate to **Latest Synced Items**.
2. Review the list of recently processed items and locate entries displaying warnings or failed synchronization indicators.
Filter conditions are evaluated at the beginning of each synchronization. If an item does not satisfy the configured filter rules, the synchronization will stop, and the item will be skipped.
### Reviewing Synchronization Logs
Once you have identified the affected item, open the synchronization details and review the logs.
The logs will typically indicate which filter condition prevented the synchronization.
For example, you may see a message indicating that a field such as **Status** does not contain any of the values required by the filter. If none of the configured values are present on the item, the filter condition will fail, and the synchronization will not proceed.
{% hint style="info" %}
Filter-related errors are usually caused by values that don’t meet the filter's criteria, values that no longer exist, outdated filter configurations, or filter operators that do not match the intended synchronization behavior.
{% endhint %}
### Reviewing Filter Configuration
After identifying the failed condition, return to your integration and review the filter settings.
Verify:
* The correct field is selected.
* The expected values exist on the source item.
* The selected operator matches the intended behavior.
For example, if the filter is configured as:
**Labels** - **contains one of**:
* Spam
* Duplicated Case
* Introduction
And if none of these values exist on the item, the synchronization will fail.
In this scenario, a **Not Contains** condition may be more appropriate depending on the desired behavior.
After making your changes:
1. Click **Apply**.
2. Click **Save** to update the integration (Changes are not applied until the integration is saved).
{% hint style="warning" %}
The filters are case-sensitive, so make sure that you are adding the same exact value, considering upper and lower case, when adding filters.
{% endhint %}
### Resyncing Affected Items
* Once the filter configuration has been corrected, return to **Latest Synced Items**.
* Locate the items that previously failed due to the filter condition.
* Click the three-dot menu and select **Resync**.
Getint will evaluate the updated filter configuration and attempt synchronization again.
***
### Understanding Multiple Filter Rules
When multiple rules are configured within the same filter category (**ALL**, **NEW**, or **SYNCED**), Getint evaluates them using the **AND** operator.
However, conditions added under the **ALL** filter category will be applied to every single item that is detected for syncing, meaning that if the work item also falls under the **NEW** or **SYNCED** filter category, it will be passed through both the **ALL** and the secondary category.
This means that an item must satisfy every rule within those categories to qualify for synchronization.
{% hint style="warning" %}
Adding additional rules makes filtering more restrictive. Review all configured rules carefully when troubleshooting synchronization issues.
{% endhint %}
### Verifying the Results
After the resync completes, return to **Latest Synced Items** and confirm that the item synchronized successfully.
The warning indicator should disappear, and the item should display a successful synchronization status.
***
### Troubleshooting
#### The Item Still Does Not Synchronize
Verify:
* The filter values exist on the source item.
* The correct filter operator is being used.
* The item meets all configured filter rules.
#### The Logs Do Not Show a Filter Error
Review:
* Integration mappings
* Authentication settings
* Reporting logs
* Connection status
The issue may be unrelated to filtering.
#### Multiple Items Are Being Skipped
Review all rules configured under:
* ALL
* NEW
* SYNCED
Remember that rules within the same category are evaluated together using the AND operator.
***
### Conclusion
By reviewing synchronization logs, validating filter conditions, and resyncing affected items, you can quickly resolve most filter-related synchronization issues. Properly configured filters help ensure that only relevant items are synchronized while maintaining reliable integration behavior.
If you continue experiencing issues, please [open a support ticket](https://getintio.atlassian.net/servicedesk/) and include the synchronization logs and filter configuration used by your integration. You can also book a [free onboarding demo call](https://www.getint.io/schedule-a-demo#book-a-demo).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.getint.io/getintio-platform/workflows/filtering-items-for-integration-in-getint/troubleshooting-sync-issues-unmet-filter-conditions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.