# Delta Sync Fails to Detect Custom-Attribute-Only Updates

**URL:** <https://community.taiga.io/t/delta-sync-fails-to-detect-custom-attribute-only-updates/7234>\
**Category:** Troubleshooting\
**Tags:** issues\
**Created:** [April 23, 2025, 11:20am UTC](https://community.taiga.io/t/delta-sync-fails-to-detect-custom-attribute-only-updates/7234 "2025-04-23T11:20:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luca](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/luca/32/4394_2.png) [@Luca](https://community.taiga.io/u/Luca)\
**Post date:** [April 23, 2025, 11:20am UTC](https://community.taiga.io/t/delta-sync-fails-to-detect-custom-attribute-only-updates/7234/1 "2025-04-23T11:20:49Z")

</div>

I’m implementing a delta-synchronization workflow against the Taiga API—fetching only those Issues that have changed (last modified date) since our last poll—to minimize data transfer and processing. While updates to core Issue fields (status, title, description, etc.) correctly appear in our delta fetch, **changes made solely to custom attributes** (e.g. Effort, Evaluation) are **not** included in the delta results. As a result:

1. When a user edits only a custom attribute value, the synchronization never sees that change.

2. It’s impossible to keep downstream systems in sync for custom-attribute data without re-fetching every Issue in full each time.

I need a way for the API’s delta mechanism to either:

- **Include** Issues when their custom attributes change, or
- Provide a separate hook or flag indicating which Issues have had custom-attribute updates, so that our delta sync can pick them up.

Without this, true incremental sync isn’t possible for custom attributes, forcing inefficient full reloads or custom polling logic.