Monitors & Alerts edit UI shows "Unknown integration" for sentry_app actions when the Sentry App has no alert-rule-action schema component

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Have a Sentry App / Internal Integration that is is_alertable=True but does NOT include an alert-rule-action element in its schema (e.g. a webhook-only internal integration).
2. Create an issue alert with an action of id: sentry.rules.actions.notify_event_sentry_app.NotifyEventSentryAppAction pointing to that app. This can be done either through automatic migration of an existing legacy alert rule, or by creating a new rule via the /api/0/projects/{org}/{project}/rules/ endpoint.
3. Open the alert in the new Monitors & Alerts edit UI at /monitors/alerts/<workflow_id>/edit/.

Expected Result

The action tile renders normally and is editable. The Sentry App integration is recognized and its settings are displayed.

Actual Result

The action tile renders with an error:
"Unknown integration"
"The integration is no longer available. Please remove and reconfigure this action."

The webhook itself continues to fire correctly when the alert triggers; only the edit UI is broken.

Affected Action rows have the shape:

• type = "sentry_app"
• config.target_identifier = "<sentry_app_id>" (numeric, already normalized)
• data = {} (empty, because the Sentry App has no UI schema component)

This reproduces for both auto-migrated alerts (legacy Rule → workflow-engine migration) and newly-created alerts via the legacy /alert-rules endpoint, since both paths translate the action through the same SentryAppActionTranslator, which always writes Action.type = "sentry_app" regardless of whether the underlying Sentry App ships an alert-rule-action schema element.

Meanwhile, the available-actions endpoint only returns Sentry App handlers (matched by app id) for apps that do ship an alert-rule-action component; apps without one are surfaced only under the webhook handler's services[] list (keyed by slug). The edit UI's handler-resolution logic for sentry_app-typed actions does not consult the webhook services list, so the lookup fails and the "Unknown integration" tile is shown.

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

Start with the available-actions endpoint and the edit UI's handler-resolution logic for sentry_app actions; trace how SentryAppActionTranslator produces the Action row. Reproduce with an alertable Sentry App lacking an alert-rule-action schema, then verify the edit tile resolves through the webhook services list and remains editable without changing webhook delivery.