Vulnerability Scanner Add Trigger Not Working

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

When trying to add a new trigger to the vulnerability scanner, it just updates the existing one rather than creating a new trigger.

Steps to Reproduce

  1. Go to existing an Vulnerability Scanner instance
  2. Click “Add Trigger”
  3. Select any scheduled trigger
  4. Notice that after making the selection, it just updates the existing trigger to be the new selection

Expected Behavior

After selecting a new trigger, the trigger should be added in addition to the existing one (similar to security reviewer behavior)

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Cursor Web App

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey there!
This is a genuine bug on our side, not something you’re doing wrong.

Right now a Vulnerability Scanner is capped at a single scheduled trigger, so “Add Trigger” ends up overwriting the existing schedule instead of adding a second one. Security Reviewer behaves differently because it uses PR-based triggers, which is why you can stack those.

Workaround until we fix this: create a separate Vulnerability Scanner agent for each schedule you want (New agent → Vulnerability Scanner). Each agent keeps its own schedule and can target its own set of repositories, which also lets you scope large repos more tightly.

I’ve reported this to our team, and I’ll follow up here once there’s an update.