<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Forking is very slow or timing out on GitLab Saas. ### Steps to reproduce - Fork the project to a personal name space with a public setting - Fork succeeds - Try to fork the same project again - Errors  ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? <!-- Describe what actually happens. --> ### What is the expected *correct* behavior? Display an error message that indicates a fork already exists. #### Option 1 > A fork of this project already exists. #### Option 2 > You have already forked this project \[project/repo-name\]. _with a link to the existing fork_