Ability to unblock CI builds if Sentry is experiencing outage/downtime

Problem Statement

At the time of writing, Sentry is experiencing a "major outage". This is, in turn, blocking my company from being able to build or deploy locally, to staging, or to production. Whenever we attempt to build our NextJS application, the build fails at the end with:

Sentry CLI Plugin: Command failed: /Users/zack/code/addition/lewis/web/node_modules/@sentry/cli/sentry-cli releases new nit4tTNbwVGr2JmDchPc6
error: API request failed
  caused by: sentry reported an error: bad gateway (http status: 502)

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.

There does not appear to be a documented workaround to allow us to disable Sentry temporarily or allow the Sentry "create new release" step to fail gracefully. As such, while Sentry is down, we are unable to work.

Solution Brainstorm

We would like a env variable or other configurable value that would allow us to either:

Disable Sentry's build post-processing
Allow Sentry's build post-processing to fail without killing the webpack build.

Adding this for context; getsentry/sentry-webpack-plugin#379

@rgegriff

Thanks @rgegriff - I didn't realize the webpack plugin was silo'd into its own repo. I see the recommendations over there and anticipate that this means someone from Sentry will show up and use that discussion as a reason to close this issue. I'm going to choose to leave it open myself, though, since I'm hoping they'll reconsider. At the very least, providing documentation and a link to it as part of the crash/failure would be IMO preferable to failing with no obvious escape hatch unless one finds that closed Github Issue and implements its suggestion.

That's fair feedback. We'll

add a log message on build failures due to Sentry CLI explaining how to unblock yourself.
properly expose the errorHandler option that is forwarded to the webpack plugin.
add docs on this whole shebang.

@lforst

🙏 thank you @lforst - that would have given me the tools I needed to sort this out yesterday.

For now you can pass to Next.js Sentry config:

unstable_sentryWebpackPluginOptions: {
  errorHandler: (err) => {
    console.log("Sentry CLI Plugin: " + err.message);
  },
},

A PR closing this issue has just been released 🚀

This issue was referenced by PR #16718, which was included in the 9.32.0 release.

Navigation Menu

Repository navigation

Ability to unblock CI builds if Sentry is experiencing outage/downtime #16195

Problem Statement

Solution Brainstorm

A PR closing this issue has just been released 🚀

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Ability to unblock CI builds if Sentry is experiencing outage/downtime #16195

Description

Problem Statement

Solution Brainstorm

Activity

rgegriff commented on May 5, 2025

zackdotcomputer commented on May 5, 2025

lforst commented on May 6, 2025

zackdotcomputer commented on May 6, 2025

raine commented on May 7, 2025

github-actions commented on Jun 25, 2025

A PR closing this issue has just been released 🚀

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions