Skip to main content

What can I do if files are not synced correctly with the associated repository?

If you have successfully linked your LingoHub project to a repository, but changes are not appearing in LingoHub after a manual or automatic pull, there are several common factors to investigate.

Common causes for sync failures

If the connection is active but the data is not updating, follow these troubleshooting steps:

1. Check the import status and event log

Every time a pull occurs, LingoHub creates an import entry.

  • Go to the Imports tab in your project. Click the specific import entry corresponding to your sync attempt.
    ​

  • Review the Event Log: This technical timeline often provides specific error messages or warnings that explain why a file was skipped or why the process stopped.

2. Verify resource filters (path matching)

A common reason for a "Success" status without any imported entries is that your Resource Filters no longer match the file paths in your repository.

  • Go to Project Settings > Integration ([Provider]) > Files.
    ​

  • Review your Include and Exclude rules. If you have renamed folders or moved files in your repository, you must update these filters to match the new paths.

  • Check the Files to be synchronized preview to ensure your filters are actually catching the intended files.

3. Check Webhook status

If you use Automatic Pull, LingoHub relies on a Webhook installed in your repository provider (GitHub, GitLab, etc.) to detect when a commit occurs.

  • If pushes to your repository are ignored by LingoHub, the Webhook may have been deactivated or deleted.

  • Log in to your repository provider and check the Webhooks section in the repository settings. Ensure the Webhook pointing to LingoHub is present and shows a "Green/Active" status.

Recommended next steps

  1. Perform a manual pull: Try triggering a pull manually from the Imports tab to see if it generates a new error message.
    ​

  2. Review branch selection: Ensure LingoHub is looking at the correct branch where the changes were committed.

  3. Validate file content: Ensure the files in your repository are not empty and follow the correct format for your project type.

Awesome! You have finished the article about troubleshooting repository synchronization. We hope this guide helped you get your files back in sync. Otherwise, contact our support, and we will gladly help!

Did this answer your question?