gitStream not scanning all Gitlab repositories that have be enabled

[brendclyde]

Describe the bug

Have been running gitStream for about 9 months on 8 of our GitLab repositories, using a global configuration, with no issues. Our GitLab Service Account (with Owner access levels), had its access token expire (expires yearly). We then regenerated a new token with: api, read_user, read_repository permissions (same as last time) , then reauthorised via the LinearB platform. Then checked/ticked the "Connect gitStream" option for each repository. The result is that gitStream now only runs on 6 of the 8 repositories, its not scanning the other 2. And not applying the rules.

To Reproduce

1.) Have a global gitStream configuration - executing on all repositories
2.) Have a Service Account with Owner access levels
3.) Have the Service Account Access Token expire
4.) Regenerate a new access token with api, read_user, read_repository permissions
5.) See if all repositories are still scanned by gitStream - even after checking/ticking the "Connect gitStream" option for each repository

Expected behavior

1.) gitStream should scan all repositories that are "ticked" to be connected to it

Screenshots

Will provide confidentially, if required.

Additional context

Please could someone from your support reach out and check our Company/Business setup/configuration

[PavelLinearB]

Hi @brendclyde, Can you please share some more information on this issue with us via email to [email protected]?

1. Do you get the label gitStream-checking or gitStream-failed in the MRs that fail to run gitStream?
   2. If so, Please share with me over the email the execution logs of gitStream for this MR
2. Please share an example MR link for:
   1. working gitStream automation (i.e., an MR from one of the 6 working repos)
   2. Non-working gitStream automation

Thanks!
Our team will start looking at this as soon as we get the data

[brendclyde]

@PavelLinearB email sent :)