[Feature request] Export Shopify Function failures to external observability tools

[zeroxtlt]

Hi Shopify Functions team,

Could Shopify expose failed Function runs to external observability tools?

Today, Function failures are only available in the Dev Dashboard. That creates an operational blind spot: merchants can be notified that a Function failed while developers may not see a corresponding actionable log, and there is no supported way to forward these failures to systems such as Sentry, GlitchTip, Datadog, or Grafana.

I am not proposing that Shopify Functions load a Sentry SDK inside the WASM runtime. A platform-level export would be more reliable because it could report failures that occur before or outside application code, including runtime exceptions, timeouts, memory or instruction-count limits, invalid modules, and invalid output schemas.

A useful implementation could provide one or more of:

• A configurable HTTPS webhook for failed Function runs
• A Sentry-compatible event or envelope destination
• An OpenTelemetry-compatible export
• Alert thresholds by Function, error type, or failure rate

The event could contain non-sensitive metadata by default:

• Function and extension identifiers
• App and Function version
• Run ID and timestamp
• Shop identifier
• Error type
• Duration, memory usage, and instruction count where available

Full Function input should remain excluded by default, with sensitive fields redacted. Delivery should support deduplication, rate limiting, and retries.

This would let app developers detect production failures quickly without polling the Dev Dashboard, while keeping observability independent from the Function’s own execution path.

Would Shopify consider adding a platform-level failure event or observability export for Functions?

[David_Arbias]

Won’t work because Shopify decided to break function logs:

Cannot debug shopify functions anymore in new version

Debugging Shopify functions is impossible now, because it shows missing “read_customers” scopes, even though the function has no PII. [Screenshot 6] If creating payment customizations need “read_customers” permissions to read fields, there shouldn’t even need to be a separate permission in the first place. This will also have an impact on merchants, since now even more apps with poor security will ask for “read_customer” scopes.

[FEATURE REQUEST] Dev Dashboard function logs: we should be able to see the allowed data depending on scopes

After the latest update regarding Shopify function logs, the “Share logs” button was removed in the Shopify Admin, and we can now automatically see the logs for which we have the necessary scopes, which is great. The problem is that when we are missing a single scope of the log, we are blocked completely from seeing the entire function log. [Screenshot 2026-06-25 at 5.45.38 PM] For example: I might need to see the shipping method of a function for debugging, but I won’t be able to do it only…

Somehow there are some apps with 3.000+ reviews that depend on this, but they haven’t come here to talk about this.

[zeroxtlt]

I think this is a separate but related issue. This proposal does not require exporting the full Function input or exposing fields restricted by missing scopes. Shopify could emit a sanitized platform-level failure event containing only non-sensitive metadata such as the Function ID, version, error type, timestamp, duration, and instruction count.

The current scope-based restrictions on Function logs are actually another reason why an independent failure notification channel would be useful: developers could at least know that a production failure occurred, even when the detailed log cannot be accessed.

[zeroxtlt]

A mockup about what I have in mind