Common problems with the GitLab catalog

What you see	What to do
Under Group: On gitlab.com, importing GitLab groups needs a Group: without one it would be every public group of gitlab.com. Enter your top-level group (for example acme); its subgroups come with it.	On gitlab.com, enter your top-level group.
On a component: This entity has relations to other entities, which can't be found in the catalog.	The owner group is not in the catalog. Check the group:gitlab/ prefix, then copy the name from the catalog.
A GitLab group is missing from Catalog › Groups	Give it a direct member in GitLab. Check it is under Group, its name is 63 characters at most and, with Group empty, its path holds no .. Then run the collection again.
The GitLab card says Ran before Astrolabe restarted: its outcome is not known. Run it now to see it.	Click the play button (Run the GitLab collection now) in the Catalog collection table.
A new project or a changed owner does not show up	The catalog reads GitLab every 30 minutes. Click the play button (Run the GitLab collection now).
The GitLab card says Configure the GitLab integration first: without it, this provider cannot read anything.	Add the GitLab integration first: GitLab › Add the GitLab integration.
In the Catalog collection table, Detail says The source does not know what the settings name (404): check the Group, the Organization or the Project in the provider's settings.	The group does not exist, or is misspelled. In Group, write it as in https://<host>/<group>.
In Administration › Problems, a Catalog block: 2 components name an owner missing from the catalog: group:gitlab/does-not-exist.	The owner group is not in the catalog. Copy the name from the catalog, then see Fix a component whose owner is not found.

Still stuck?

Write to support@forgeit.fr with the name of the component or the group.