Sourcetree Remote Fetch Cache Invalidation Configuration

Confirmed facts

Sourcetree maintains a local cache of remote branch references to avoid repeated network requests. The cache timeout and enable/disable toggle are found in Preferences → General → Remote repository caching (macOS) or Tools → Options → General → Remote repository caching (Windows). A Clear Cache button in the same section forces an immediate refresh.

Likely explanation

There is no per‑fetch trigger that automatically invalidates the cache right after a remote fetch. The cache is only refreshed after the configured timeout expires or when the user clicks Clear Cache (or manually refreshes the view). Lowering the timeout makes the cache expire sooner, which updates the ahead/behind counts more frequently, but it does not guarantee an immediate update after each fetch.

Steps to configure

1. Open Sourcetree preferences: Sourcetree → Preferences (macOS) or Tools → Options (Windows).
2. Select the General tab.
3. Locate the Remote repository caching section.
4. Adjust the timeout value (e.g., set to 5 minutes) to make the cache expire sooner.
5. Optionally uncheck Enable remote repository caching to disable caching entirely, causing a fetch on every remote operation.
6. Click OK to save.
7. To verify, perform a fetch, then wait the timeout period (or click Clear Cache) and check that the ahead/behind numbers update without pressing F5.

What to verify

• After changing the timeout, watch the Last fetched timestamp in the remote branches view; it should update roughly after the specified interval.
• Click Clear Cache and then refresh the remote branch list; the list should be repopulated from the server.
• If you disabled the cache, each fetch should contact the remote (visible in the console log if logging is enabled).

If you are using a version of Sourcetree where the menu layout differs (e.g., older 2.x releases), please let me know the exact version number so I can confirm the precise location of the caching settings.