- 
    
Bug
 - 
    Resolution: Fixed
 - 
    
Low
 - 
    9.4.0
 
- 
        Severity 3 - Minor
 - 
        
 
Issue Summary
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Enable profiling
 - Disable fork syncing in a forked repo that has fork syncing enabled
 
Expected Results
The profile log shows "Disabling synchronization"
Actual Results
The profile log shows "Enabling synchronization"
2025-01-03 08:27:44,037 | http-nio-7990-exec-3 | *1D23ANGx507x21311x0 | user | lbxmul [35.6ms] - "POST /rest/sync/latest/projects/~USER/repos/fork HTTP/1.1" [2.7ms] - Project com.atlassian.bitbucket.project.ProjectService.getByKey(String) [1.2ms] - InternalProject com.atlassian.stash.internal.project.ProjectDao.getByKey(String) [1.4ms] - boolean com.atlassian.stash.internal.user.ProjectPermissionDao.isGrantedToUser(int,int,Permission) [1.1ms] - InternalRepository com.atlassian.stash.internal.repository.RepositoryDao.getBySlug(String,String) [13.4ms] - 12: Enabling synchronization
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available