---
title: "TFS4JIRA Self-Hosted - Automatic Scheduled Synchronization not working"
canonical: "https://support.appfire.com/space/SUPPORT/349503687/TFS4JIRA%20Self-Hosted%20-%20Automatic%20Scheduled%20Synchronization%20not%20working"
format: markdown
---
Please keep in mind that the app is always improving over time. This issue may not appear on the current version of the TFS4JIRA application.

This page is for a **Self-Hosted **environment.

### TFS4JIRA version: 7.10.30

## Issues

- Automatic Scheduled is not working when trying to sync from **Jira → TFS**.
- The scheduled SYNC tool detected only a few TFS changes and have to do `Initial Synchronization` to make the sync, able to work.
- It only happens when there are new values in TFS that have not been added to JIRA.
- It does not detect the change *- ****“TfsItemsSource - Found 0 item(s) to sync”***
- Following is the log:

## Resolutions

- For this version, in general, we have a bug from our end, where we will not fetch issues during the synchronization.
- The reason that the log has **Found 0 item(s) to sync** is when the sync happens, and something is updated during that sync, we will not sync that data until that issue ***is updated again*****.**
- For example:

> ℹ️ - If the sync starts at 09:00, the update on the work item occurred at 09:01, and the sync ends at 09:03. We only store in the DB that the last sync ended at 09:03, while the update of a workitem happened at 09:01.
> ℹ️ - Hence, the next sync loop will only fetch the updated workitems >=09:03.   
> ℹ️ It will only fetch the workitems if the issue is **updated again** after that.


- The proposed solution is to **extend/increase** the sync interval to 30 minutes so that it can fetch the data within that period of time if there is an update to the work items.
- If the customer is using the old version, advise them to upgrade to the latest version.

> 📝 The improvement for this behavior is on to-do list, but unfortunately now we cannot prioritize it as it is not a blocker.