It's possible that the webhook isn't set up for the CI job. The CI job webhook is how your Version Control System (e.g. GitHub) communicates with your CI job.
What's the impact on the CI job?
Lack of webhook set up would impact your CI job in a way that the job will not run. Even if the changes have been merged in the source branch (for example via a PR merged in your Pipeline).
How to check wehhook configuration?
You can do so by clicking on Webhook setup... on your CI jobs page (also referred to as CI dashboard).
If a webhook is correctly set up, you'd see a pop up window like this:
If the webhook isn't set up, you will need to configure it. To minimise error, we recommend letting Gearset automatically create your webhook.
You may also try resetting your webhook if it's already configured. We recommend resetting it in scenario where your CI job didn't run at all.
Note: If you're using AWS CodeCommit, automatically creating webhooks is not an option. You can find a guide on how to configure AWS CodeCommit webhooks here.