StatusCake App Availability cannot scope monitors to the audited product

[filipenevola]

Summary

The StatusCake App Availability integration check evaluates every monitor in the connected StatusCake account. A single down monitor for an unrelated product/service makes the compliance task fail, even when all monitors relevant to the scoped audit product are healthy.

This creates a false scope result for organizations that use one StatusCake account for multiple products or customers.

Reproduction

1. Connect a StatusCake account that contains monitors for multiple products/services.
2. Attach/run the StatusCake App Availability check for a compliance task scoped to one product.
3. Keep all in-scope product monitors healthy.
4. Have one unrelated monitor report down.
5. Run the check.

Actual result

• The run reports one failed finding for the unrelated monitor.
• The task is marked failed.
• There is no visible configuration to select or exclude StatusCake monitors for this task/check.

Observed again on 2026-08-15 using the hosted Comp AI platform. The run completed without an API error and reported one passing aggregate result plus one finding from the unrelated monitor.

Expected result

Provide an explicit, auditable scope mechanism, for example:

• allowlist monitor IDs per connection/check/task;
• tags/groups/project selection; or
• an exclusion list with recorded justification.

Only selected in-scope monitors should affect the compliance task status. Unselected monitors may remain visible as informational context but should not fail the scoped task.

Compliance impact

Without scoping, the check can both:

• falsely fail an audit task because of an unrelated service; and
• encourage disabling legitimate monitoring outside the audit scope merely to make the compliance check pass.

No organization IDs, connection IDs, run IDs, monitor IDs, customer names, or private URLs are included in this report.

[linear-code]

COMP-293

[filipenevola]

Additional affected check verified on 2026-08-17: the same account-wide scoping problem also affects the StatusCake Incident Response check. A connected account with multiple products had 9 healthy contact groups and one empty contact group belonging to an unrelated service. The unrelated group produced a high-severity finding and kept the audit-scoped Incident Response task failed. The check has no visible task-level allowlist, tag/group selector, or justified exclusion for contact groups. Please include incident-response routing resources in COMP-293 scope, not only uptime monitors. This reproduction includes no organization, connection, run, contact-group, customer, or private URL identifiers.