@kapa.ai why is my incremental sync not seeing changes on my source? It has refused to sync new updates

There could be several reasons why your incremental sync is not picking up changes from your source. Here are some possibilities based on the knowledge sources provided: 1. Cursor Field Not Updated: Incremental sync in Airbyte relies on a cursor field to track changes. If modifications to the underlying records are made without properly updating the cursor field, then the updated records won't be picked up by the incremental sync as expected. The source connectors extract delta rows using a SQL query that looks for records where the cursor field is greater than the last sync's max cursor field value. If this field is not updated correctly, new changes won't be detected. [source](https://docs.airbyte.com/using-airbyte/core-concepts/sync-modes/incremental-append#known-limitations) 2. Limitations of Incremental Sync: Incremental sync has some known limitations. For instance, it cannot handle source schema changes yet, such as when a column is added, renamed, or deleted from an existing table. In such cases, it is recommended to trigger a Full refresh - Overwrite to correctly replicate the data to the destination with the new schema changes. [source](https://docs.airbyte.com/using-airbyte/core-concepts/sync-modes/incremental-append#known-limitations) 3. No Modifications Made: If a sync is executed without making any modifications on the source database, no records will be emitted, and no changes will be made on the destination database. [source](https://airbyte.com/tutorials/incremental-data-synchronization#step-7) 4. Issues with the Connector: There have been reported issues with certain connectors not picking up changes correctly in incremental mode. For example, the Stripe connector had an issue where the new events-based incremental sync didn't capture updates. [source](https://github.com/airbytehq/airbyte/issues/31917) If you're still facing issues, it would be helpful to check the logs for any errors or unusual behavior during the sync process.