You’re right that it’s still happening, and this is on our side, not your setup. The change we made to GitHub webhook handling improved many org-repo cases, but it doesn’t fully cover yours: when an organization’s Cursor GitHub App is still tied to the team setup you used previously (and your current account is personal, with no team), webhooks from the org repo can’t be matched to your personal automation, so the run gets silently skipped.
Two things that often get this working again in the meantime:
Re-connect GitHub from your dashboard. Go to cursor.com/dashboard/integrations, disconnect and reconnect GitHub, and when prompted use Manage in GitHub to re-authorize the organization. This re-maps the org’s installation to your current account and has cleared similar org-connection issues for other users.
If the org repos sit under a team, connecting them through a Cursor team account (rather than a personal one) is the more reliable path for org-repo automations.
To pin down your exact case, could you share:
The organization / repository the automation targets (feel free to send it privately), and
Whether the automation triggers when you personally open the PR or issue, or never fires at all for that org repo.
That second answer tells us right away which part of the flow is dropping the event. I’m taking another look at this with the team in the meantime.