Skip to main content

Events

An event is something Merge Pilot announces: a merge without approval, a change approval waiting for a decision, secrets found in a merge request, a connection that stopped working. Each notification route picks the events it takes (see Routes), and some events are also emailed to the people they concern (see Personal notifications). This page lists every event.

How to read the list​

  • Event is the label of the route's checkbox on the Notifications tab and of the switch in My profile → Notifications. The checkbox's tooltip shows the API value, which is also the event of a webhook delivery and the value in a route's events list. Every event (all) takes all of them, including events added later.
  • Sent when says what raises the event. Sent once per says what makes it new: the same event about the same thing in the same state is sent once, however often Merge Pilot notices it, and checks running at the same moment send it once too. Where a time is given (within an hour), the same event is sent again only after that time.
  • Title and Message are what Slack, Teams and email show. MR !12 / PR #12 and MR / PR follow the project's VCS (GitLab merge requests, GitHub pull requests); group/app stands for the project's path (repo <id> when the repository is not registered in Merge Pilot); KEY-1 for the change approval's key in the tracker. Titles are one line of at most 120 characters, messages at most 2,000 (see Message content).
  • Colour is the bar or title colour: green (good), amber (warning) or red (danger).
  • Opens is the page the message's Open in Merge Pilot link goes to.
  • Personally to is who gets the event by email besides the routes (see Personal notifications). Every personal email is on until the person turns it off, except Connection recovered, which is off until they turn it on. A dash: routes only. Nobody is emailed personally about their own action (an admin who turns a connection off gets no email about it; the other admins do). The routes still get the event.

Nothing is sent for some merge requests and repositories whatever the routes say: see What holds events back.

Merge requests​

Event (label in the UI)API valueSent whenSent once perTitleMessageColourOpensPersonally to
Merge request evaluatedmr_processedA standard change passed the checks of its policy and its merge gate turned approved. Other change types do not send itHead commitMR approved (standard change)MR !12 (group/app) passed the checks of policy Name and may mergeGreenThe merge request—
Merge request blockedmr_blockedThe merge gate holds a merge request because a blocking control failed, and its policy does not close it. Not for imported past merge requestsHead commit and set of failing controlsMR blocked; MR would be blocked in a watched repositoryMR !12 (group/app) cannot merge under policy Name: <why>; in a watched repository … would be blocked under policy Name: <why>. Its repository is watched, so nothing was writtenRedThe merge requestThe author
Merge request refusedmr_rejectedA policy rejected and closed the merge request (Close the merge request, see Merge gate)Head commitMR rejectedMR !12 (group/app) was rejected and closed: <reason>RedThe merge requestThe author
Not enough approversmr_approvers_shortFewer people may approve the change than its policy needsHead commitNot enough approversMR !12 (group/app) needs 2 approvals under policy Name, but only 1 person may approve it (… but nobody may approve it)RedThe merge requestThe author
Risk assessedmr_risk_assessedA head commit was assessed high or critical risk (see Risk). The new score at merge time sends nothingHead commitMR high risk, or MR blocked for its risk when the risk blocks the mergeMR !12 (group/app) was flagged, risk level high (or was blocked, risk level critical)Amber; red when blockedThe merge request—
Merge request mergedmr_mergedA merge request was mergedMerge requestMR mergedMR !12 (group/app) was merged by aliceGreenThe merge request—
Merged without approvalmr_merged_without_approvalA merge request under change management was merged without an approved change approval (also one merged before Merge Pilot evaluated it)Merge requestMR merged without approvalMR !12 (group/app) was merged by alice without change-management approvalRedThe merge request—
Merged during a change freezemr_merged_in_freezeThe change was merged during a change freeze that held it (see Change calendar)Merge request and freezeMerged during a change freezeMR !12 (group/app) was merged by alice during the change freeze Name, which held itRedThe merge request—
Separation of duties brokenmr_sod_violationSomeone who approved the change merged it, and the policy does not allow it (see Separation of duties)Merge request and approverSeparation of duties brokenMR !12 (group/app): alice approved the change and merged it, which its policy does not allowRedThe merge request—
Approval revoked after mergemr_approval_revoked_after_mergeThe change approval of a merged change was withdrawn in the tracker (see Change approval lifecycle)Merge request and change approvalApproval revoked after mergeMR !12 (group/app) is merged, but the approval of change approval KEY-1 was withdrawn in the trackerRedThe change approval—
Emergency declaredemergency_declaredA change was declared an emergency (see Emergency changes)Merge request, policy and who declared itEmergency change declaredMR !12 (group/app) was declared an emergency by bob (policy Name): it may merge before it is approved (its author when nobody else is named)AmberThe merge requestCompany admins
Emergency review overdueemergency_review_overdueThe review of an emergency change was not decided by its deadline (see Review deadline)Change approvalEmergency change review overdueThe review of emergency change MR !12 (group/app) in change approval KEY-1 is past its deadlineRedThe change approvalCompany admins

Change approvals​

Event (label in the UI)API valueSent whenSent once perTitleMessageColourOpensPersonally to
Change approval createdchange_approval_createdA change approval was opened for a merge request (see Change approval lifecycle)Change approvalChange approval createdChange approval KEY-1 was created for MR !12 (group/app)GreenThe change approvalThe assignee; when nobody was assigned, everyone who may decide it
Change approval approvedchange_approval_closedA change approval was approved, in the tracker or in Merge PilotChange approval and decision round: approved again after its approval was revoked, or after it was reopened for new commits, it is sent againChange approval approvedChange approval KEY-1 was approved, so MR !12 (group/app) is approvedGreenThe change approvalThe author
Change approval rejectedchange_approval_rejectedA change approval was rejected, in the tracker or in Merge PilotChange approval and decision roundChange approval rejected: MR closed when the policy closes the merge request, else Change approval rejected: MR blockedChange approval KEY-1 was rejected, and its policy closes MR !12 (group/app), or Change approval KEY-1 was rejected: MR !12 (group/app) stays open and cannot mergeRedThe change approvalThe author
Change approval reassignedchange_approval_reassignedSomeone took over a change approval from its assignee (Take over, see Voting), or a change approval nobody could take was assigned once someone couldThe same handover, within an hourChange approval reassignedbob took over change approval KEY-1 of MR !12 (group/app) from alice, or Change approval KEY-1 of MR !12 (group/app) is now assigned to bobAmberThe change approvalThe new assignee
Change approval due soonchange_approval_due_soonA change approval's deadline is near (a quarter of its time, at most a day, see Change approval deadlines): a normal change's change approval deadline, or an emergency change's review deadlineChange approval and deadlineChange approval due soonChange approval KEY-1 of MR !12 (group/app) is due on 2026-10-30 14:00 UTC; for an emergency change The review of emergency change MR !12 (group/app) in change approval KEY-1 is due on …AmberThe change approvalThe assignee
Change approval overduechange_approval_overdueA normal change's change approval is past its deadline and still not decidedChange approval and deadlineChange approval overdueChange approval KEY-1 of MR !12 (group/app) was due on 2026-10-30 14:00 UTC and is still not decidedRedThe change approvalThe assignee
Approval fatigueapproval_fatigueAn approver's decision raised an approval concentration warning (see Approval fatigue)Approver, within the company's lookback daysApproval concentration warningMR !12 (group/app): alice approved 25 change approvals in the last 7 daysAmberThe merge request—

Opens: the change approval is the issue in the built-in tracker when the change approval is there, and the merge request otherwise (an issue in Jira is not a page of Merge Pilot).

Change approval deadlines​

A normal change's change approval can have a deadline: Change approval deadline (hours) on the company's Approvals tab, which a policy's approval control can replace with its own Change approval deadline (see Approval → Change approval deadline). The deadline is set when the change approval is created. Emergency changes keep their policy's review deadline.

A change approval that is opened again gets a new deadline, counted from that moment with the same hours: reopened for new commits, or its approval revoked in the tracker. What was sent about the old deadline does not hold back the new one's notices.

Change approval due soon is sent when a quarter of the time to the deadline is left, and at most a day before it: a day before a deadline of four days or more, 6 hours before a 24-hour deadline, 30 minutes before a two-hour one. Once the deadline passes and the change approval is still open, Change approval overdue is sent (for an emergency change, Emergency review overdue). Merge Pilot checks every few minutes; each is sent once per deadline, and an audit entry is written with it.

Scan findings​

Event (label in the UI)API valueSent whenSent once perTitleMessageColourOpensPersonally to
Secrets found in a merge requestsecrets_detectedThe secret scan of a merge request found potential secrets (see Secret scan)Head commit and number of findingsSecrets found in MRMR !12 (group/app): 3 potential secrets found in the diffRedThe merge requestThe author
Vulnerable dependency introduced by a merge requestvulnerabilities_detectedThe dependency scan of a merge request found vulnerabilities it introduces (see Dependency scan)Head commit, number and worst severityVulnerable dependencies in MRMR !12 (group/app) introduces 2 dependency vulnerabilities (1 critical)Red when one is critical, amber otherwiseThe merge requestThe author
Malicious package in a merge requestmalicious_package_detectedA merge request adds packages known to be maliciousHead commit and numberMalicious package in MRMR !12 (group/app) adds 1 package known to be malicious: remove themRedThe merge requestThe author
Denied license in a merge requestlicense_deniedA merge request adds dependencies under a license the company denies (see Licenses)Head commit and numberDenied license in MRMR !12 (group/app) adds 2 dependencies under a license the company deniesRedThe merge requestThe author
Dependency source problems in a merge requestdependency_sources_detectedA merge request's dependency files take packages from sources the dependency source check fails (see Dependency sources)Head commit and numberDependency sources to check in MRMR !12 (group/app): 2 dependency source problems in the dependency filesAmberThe merge requestThe author
CI configuration problems in a merge requestci_config_problemsThe CI configuration a merge request changes has problems (see CI configuration check)Head commit and numberCI configuration problems in MRMR !12 (group/app): 2 problems in the CI configuration it changesAmberThe merge requestThe author
Vulnerable container images in a merge requestimage_vulnerabilities_detectedThe container image scan of a merge request found vulnerable packages in the images it adds or changes (see Container image scan)Head commit, number and worst severityVulnerable container images in MRMR !12 (group/app): 5 vulnerabilities in 2 container images it refers to (1 critical)Red when one is critical, amber otherwiseThe merge requestThe author
Infrastructure problems in a merge requestiac_problems_detectedThe infrastructure check of a merge request found misconfigurations it brings into the files it changes; those the target branch already has are left out (see Infrastructure check)Head commit, number and worst severityInfrastructure problems in MRMR !12 (group/app): 3 problems in the infrastructure files it changes (worst: high)Red when the worst is critical, amber otherwiseThe merge requestThe author
New vulnerability on a default branchvulnerability_foundA round of checks found new vulnerabilities on default branches, at or above the company's threshold (see Vulnerability inventory). The baseline and findings an exception covers are not announcedOne digest per round of checksNew vulnerabilitiesNew vulnerabilities on the default branch of group/app: (or … on the default branches of 3 projects:) then one line per finding, worst first, at most 10: • <advisory> <package>@<version> (<severity>), with in <project> when there are several projects, , fixed in <version> and , introduced by MR !12 when known; +N more for the restRed when the worst is high or critical, amber otherwiseInsights → Vulnerabilities—

Each scan finding is its own event: a merge request with secrets and a denied license sends both, and each is sent without the others.

New vulnerability on a default branch collects the findings of every project in a round into one message per route. A route with path patterns gets only the projects it matches; a route with Stop here keeps the projects it took from the routes after it. A round still waiting for its last checks after an hour sends what it has.

Repositories​

Event (label in the UI)API valueSent whenSent once perTitleMessageColourOpensPersonally to
Direct change to a watched branchdirect_changeA change reached a watched branch without a merge request, and the company announces direct changes. Not for ignored accounts. See Direct changes → NotificationsChange: the branch moving on from the head Merge Pilot last saw (a push delivered again, or found by both the push and the head check, is sent once). A branch deleted again, restored and deleted again, or force-pushed back, is a change of its own and is sent and recorded again. The first change to a branch is sent at once; further ones to it within the next 15 minutes are sent together, in one notification, when the 15 minutes endDirect change to <branch>; for the 15 minutes' further changes, N more direct changes to <branch>alice pushed 2 commits to main of group/app without a merge request; alice force-pushed main of group/app, rewriting its history (2 commits not from a merge request); alice deleted the branch main of group/app; then . The branch is under change management: this is a violation or . Change management would have blocked it. Someone (found by the head check) when the pusher is not known. Further changes: 2 more direct changes were made to main of group/app without a merge request within 15 minutes of the first one (3 commits not from a merge request), by alice, bob. Its head is now 1a2b3c4d (or The last one deleted the branch), then . The branch is under change management: these are violations or . Change management would have blocked themRedThe projectCompany admins
Branch protection weakenedprotection_weakenedThe branch protection check found that a repository under change management lets changes skip the merge gate, or found other gaps than last time, and the company announces direct changes (see Repositories settings). Fixing the gaps sends nothing; when gaps come back, it is sent againProject and set of gapsBranch protection weakenedChanges can reach the target branches of group/app without change management: then one line per gapRedThe projectCompany admins
API token expiringapi_token_expiringA personal API token expires within 14 days, then within 3 days (see API tokens)Token and warningAPI token <name> expires in <N> daysThe API token deploy (mpt_ab12_…) expires on 2026-12-01 UTC and cannot be extended. Create a new token under My profile → API tokens, put it where this one is used, then delete this oneAmberMy profileIts owner
Service API token expiringservice_token_expiringA service API token expires within 14 days, then within 3 daysToken and warningAPI token <name> expires in <N> days…Create a new token under the company's API tokens…AmberThe company's API tokens tabCompany admins
Connection token expiringconnection_token_expiringThe token a GitLab connection uses expires within 14 days, then within 3 daysConnection, expiry and warningToken of <connection> expires in <N> daysThe token of the GitLab connection GitLab expires on 2026-12-01. Then Merge Pilot can no longer reach the VCS: create a new token on GitLab for the same account and enter it on the connectionAmber (red within 3 days)The company's Connections tabCompany admins
Change approvals of a deactivated personchange_approval_assignee_deactivatedA person deactivated in Merge Pilot was assigned open change approvals (see Approvals → When an assignee is deactivated)Person and set of change approvalsChange approvals of <person>, deactivatedalice was deactivated while assigned 2 open change approvals (CMG-12, CMG-14): they are assigned again by their policies' rules (or …: they stay assigned to alice until someone takes them over)AmberThe merge requestsCompany admins
Protection removed from a governed branchbranch_unprotected_by_adminA company admin removed the protection of a branch under change management through Merge Pilot (see Branch protection)Every removalProtection removed from <branch>alice removed the protection of main in group/app, a branch under change management. Changes can now reach it without the merge gateRedThe projectCompany admins

Connections and sign-in​

Event (label in the UI)API valueSent whenSent once perTitleMessageColourOpensPersonally to
Connection problemconnection_unhealthyA connection got a problem it did not have: the VCS refuses Merge Pilot's credentials, the GitHub App (or an installation) lacks permissions Merge Pilot needs, the VCS's API rate limit is used up, or an admin turned the connection off. See Connection health and How connection health is decidedProblem, within an hour; an admin turning the connection off, every timeConnection problem: <connection>The GitLab connection Name has a problem: the VCS refused Merge Pilot's credentials (or … the GitHub App lacks permissions Merge Pilot needs, or an installation has not accepted them, … the VCS's API rate limit is used up: background work waits until it resets, … it was turned off)RedThe company's Connections tabCompany admins
Connection recoveredconnection_recoveredThe connection's problem is gone, or it was turned on again, and that problem was announcedAnnounced problem; turned on again, every timeConnection recovered: <connection>The GitLab connection Name works again. The problem was: …, or The GitLab connection Name was turned on againGreenThe company's Connections tabCompany admins, off until they turn it on
Identity provider unreachablesso_check_failedWhen a session was refreshed, Merge Pilot could not ask the identity provider whether the person may still sign in; the person is asked to sign in again (see Identity providers)Identity provider, within an hourIdentity provider unreachable: <provider>Merge Pilot could not ask the identity provider Name whether people may still sign in, so they are asked to sign in againRedThe company's Sign-in tabCompany admins
LDAP directory unreachableldap_check_failedThe same for the company's LDAP directory (see LDAP directory)Within an hourDirectory unreachableMerge Pilot could not ask the company's LDAP directory whether people may still sign in, so they are asked to sign in againRedThe company's Sign-in tabCompany admins

How connection health is decided​

Merge Pilot checks every connection regularly, and when an admin clicks Test on it. A problem is cleared only by a check that uses the same credentials that failed:

  • GitLab: the check uses the connection's token, the one all work uses. A working check clears credentials refused and rate limit used up.
  • GitHub App: the check first calls GitHub as the App, then with each installation's token, the credentials all work uses (a call that does not use up the rate limit). A refused installation token keeps the problem even while the App itself answers, until every installation Merge Pilot can use works again. Suspended installations, and installations removed on GitHub, do not count: they show on the connection (see GitHub App installations). An installation whose rate limit is used up shows rate limit used up. Permissions missing is decided from the permissions last read from GitHub, by the regular check and by Test alike.
  • Rate limit hit by a background job: when the VCS gave a reset time (its Retry-After, or the limit's reset), the problem stays until that time has passed, even if a check works: a check cannot see every limit a job can hit. A limit a check finds itself is looked at again by the next check.
  • Rate limit kept for live events: when only the share of the hour's calls kept for webhooks and people's actions is left, background work waits. Rate limit used up stays until the limit resets, even if a check works.

The same problem is announced once within an hour: a connection that keeps failing and recovering does not flood the routes. A recovery is announced only when its problem was: a problem held back by the hour leaves its recovery unannounced too, so the announcements always alternate. When nothing of a connection event could be queued, the change is taken back and made again by the next check. The connection's state on the Connections tab is always current.

People and the platform​

Event (label in the UI)API valueSent whenSent once perTitleMessageColourOpensPersonally to
Role changeduser_role_changedA person's role changed, by an admin, or by their identity provider's or company directory's groups at sign-inEvery changeRole changed: <user>alice's role changed from user to policy_manager (by bob) (or (by the identity provider Name), (by the company directory))AmberThe Users pageThe person whose role changed
VCS access to reviewaccess_releasedMerge Pilot stopped tracking access it gave on the VCS, or tokens it created, which may still work there: a person was deactivated, moved to another company, made platform admin or unlinked their VCS account, a project was removed, a connection deleted or the company deactivated (see People)Every releaseVCS access to reviewMerge Pilot stopped tracking 2 access grants and 1 token of alice because the person was deactivated. They may still work on the VCS: review them under the company's peopleAmberThe company's People tabCompany admins
License expiringlicense_expiringMerge Pilot's license expires in 30, 7 or 1 days, and once more when it has expired and its grace period starts (see Platform settings). Sent to every active companyExpiry date and thresholdLicense expires in 7 days; when the grace period starts, License expired: grace period until 2026-11-20Merge Pilot's license expires on 2026-11-06 00:00 UTC. A platform admin renews it under Settings; when the grace period starts, Merge Pilot's license expired on … UTC. It keeps working until … UTC, then stops taking events from the VCS and trackers. A platform admin renews it under SettingsAmber; red at 7 days or fewer, and when the grace period startsNo linkCompany admins
Background job failedjob_failedA background job of the company failed its last attempt (see Jobs). A failure that shows a connection problem is sent as Connection problem instead; a change approval that keeps failing to open for the same reason is reported onceVCS connection and kind of failure, within an hourBackground job failedThe secret scan job <job ID> for MR !12 (group/app) failed after its retries: the credentials were refused. The full error is in the audit logRedInsights → Jobs—
Notification not deliverednotification_failedA delivery to a route failed for good (see Delivery log and failures). Never sent to the route that failed, and not for a failed route test or a failed personal emailRoute and kind of failure, within an hourNotification not delivered: <route>A secrets_detected notification could not be delivered to the route Name: the endpoint answered 500. Its deliveries are in the delivery logRedThe company's Notifications tabCompany admins

Background job failed says what kind of failure it was (the credentials were refused, permission denied, rate limited, TLS certificate problem, timed out, a server could not be reached, not found, a server answered with an error, or an internal error), never the error itself: errors can name internal hosts and addresses. The full error is in the audit log (job_failed).

What holds events back​

Before any route or person is looked at:

WhatWhat it holds back
Imported merge requestsEvents about merge requests imported from the history are never sent
Merge requests left watchedA merge request recorded while its repository was watched stays watched after the repository moved to change management, and never sends events
Watched repositories (What is announced, off by default)While it is off, events about a watched repository or a watched merge request are not sent to any route or person, webhooks included. See What is announced
Direct changes (What is announced, on by default)While it is off, Direct change to a watched branch and Branch protection weakened are not sent
New vulnerabilities on default branches (What is announced, High and above by default)The lowest severity that New vulnerability on a default branch announces; Never sends none

Some events are never sent for watched merge requests whatever the settings, because nothing is written for them: Merge request evaluated, Emergency declared, and Merge request refused (a watched merge request is never closed). A watched merge that change management would have held, or that falls in a change freeze, is recorded on the merge request as evidence and not sent. See Watching repositories.