# Troubleshooting

# Why is my analysis timing out?

At the moment, DeepSource has a hard limit of 25 minutes to publish the analysis results. If the analysis fails to finish within the allotted time, we show an Analysis timed out message.

It is more likely to happen for the first-ever analysis run for a repository, where all files are analyzed.

If your repository has files that you don't want to run analysis on (like migrations, examples, fixtures, etc) please make sure they are specified in the exclude_patterns in the .deepsource.toml config file.

Note: Even if the analysis gets timed out for the first run, DeepSource will continue to analyze every incoming commit/PR after it is activated for the repo.

# Why do I see test coverage issues for lines that have not changed in my PR?

It happens when the PR is not rebased with the default branch. Rebasing the PR will fix this problem.

# DeepSource generated a wrong autofix. How do I report it?

Report it to support@deepsource.io with a screenshot, or the code snippet for which the wrong autofix was generated.

Last Updated: 11/27/2020, 4:27:25 PM