Hi @gdschl ,
Based on the GitProviderErrorCode 502 you're encountering, it's highly likely that the sporadic failures are due to the large 30 MB size of your dashboard file. This points to a network or server-side timeout issue when processing the large file during the Git sync operation. A 502 Bad Gateway error from nginx, as seen in your error response, typically means that a server acting as a proxy did not receive a timely or valid response from the upstream server handling the actual Git operation. This is a known issue, as other Microsoft Fabric users have reported the exact same problem with large files.
The most direct approach to fix this is to reduce the size of the .pbix file itself. You can achieve this by optimizing your data model. Review your data imports in Power Query to ensure you are only bringing in necessary columns and rows. Additionally, use the Performance Analyzer in Power BI Desktop to identify and optimize any slow-running visuals or complex DAX measures that could be contributing to the large file size.
However, the recommended best practice for using Power BI with Git source control is to convert your .pbix file to the Power BI Project (.pbip) format. When you save your work as a .pbip, the report and dataset definitions are stored as smaller, human-readable JSON files. These small text-based files are ideal for version control and avoid the timeout issues associated with large binary files. The large data model is separated into a file that can be excluded from your repository.
To implement this, you would use a .gitignore file to prevent the large data files from being committed. This ensures your Git operations remain fast and reliable.
# Ignore Power BI files that are not source code
*.pbix
*.pbit
*pbidataset.json
*pbidatasource.json
# Ignore model data
*.bim
By committing only the small definition files, you align with best practices for source control and should eliminate the 502 errors. If the problem continues after trying these solutions, you can consult the official Troubleshoot the Fabric lifecycle management tools. - Microsoft Fabric | Microsoft Learn or consider opening a support ticket with Microsoft, providing them with the Activity ID and Request ID from your error log.
Best regards,
