On this page
Is Shortcut Down? How to Tell and What to Do
Shortcut (formerly Clubhouse) is a project management platform built for software engineering teams. It organizes work into stories, epics, and sprints, integrates with GitHub and GitLab for automated PR linking, and serves as the single source of truth for engineering backlog. When it goes down, sprint planning stalls, GitHub integrations break, and engineering teams lose visibility into what's in progress.
Statusfield brings reported Shortcut incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
Follow Shortcut incidents with your team
Statusfield brings reported status for Shortcut together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
Common Signs of a Shortcut Outage
| Symptom | What's likely happening |
|---|---|
| Shortcut dashboard won't load | Web application layer is unavailable |
| Stories not updating when PRs are merged | GitHub / GitLab integration is degraded |
| Workflow state transitions not saving | State machine or persistence layer is failing |
| Search returning no results or errors | Search index is degraded |
| Automations not triggering | Workflow automation engine is failing |
| API calls returning 5xx errors | REST or GraphQL API layer is degraded |
| Notifications not sending | Notification delivery pipeline is failing |
How to Confirm It's Shortcut, Not You
1. Try loading a specific story URL
Navigate directly to a story URL (shortcut.com/[workspace]/story/[id]). If it returns an error or fails to load, the web application is down — not a configuration or browser issue.
2. Check GitHub integration from both sides
Create a test branch with a Shortcut story ID in the name and push it. If the branch doesn't appear in the Shortcut story's "Branches" section within a minute, the GitHub integration webhook is failing.
3. Test the API directly
Run a simple API call against the Shortcut API endpoint. If it returns a 5xx error or times out, the API layer is degraded — confirm with a minimal GET /api/v3/member call.
4. Check with a teammate
If a colleague on a different network is experiencing the same loading errors, it confirms the issue is with Shortcut's infrastructure — not your network or browser cache.
Use vendor reports as investigation context
Statusfield brings reported Shortcut incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
A reported incident can help you decide where to investigate and what to tell your team. An operational status does not prove that your account, region or complete workflow is working. Review the affected components and timestamps alongside your own logs and checks.
What to Do During a Shortcut Outage
Immediate (first 5 minutes)
- Identify the scope — is the full web app down, or just specific features (GitHub integration, automations, search)? Full app outages affect all workflows; integration failures are scoped to automated updates.
- Alert your engineering team via Slack — prevent everyone from independently debugging their setups when the issue is platform-wide.
- Do not run sprint ceremonies — sprint planning or retrospectives that depend on the Shortcut board should be delayed until the platform is stable. Running a sprint on a stale board creates noise.
- Pause any bulk workflow automation — if you have automated state transitions running, pause them to avoid partial state updates during the outage.
Communication (first 15 minutes)
- Post a Slack message to your engineering channel with the outage status and an ETA based on typical Shortcut resolution times.
- Notify your eng manager or scrum master — sprint planning sessions should be rescheduled if the board is unavailable.
- If you're in the middle of a release cycle, track story status manually in a shared doc during the outage rather than losing visibility entirely.
Recovery
- After Shortcut recovers, verify that GitHub/GitLab PR events that fired during the outage have been replayed — some integrations replay missed webhooks, others don't.
- Check for missed workflow automation triggers — stories that should have moved to a new state may be stuck.
- Run a quick search to confirm the search index is back to current state.
- Review automations log for any failed runs during the outage window.
Shortcut Components and What Each Outage Looks Like
| Component | Impact when degraded |
|---|---|
| Web application | Dashboard, stories, and epics inaccessible |
| GitHub / GitLab integration | PRs not linking to stories; branches not appearing |
| REST / GraphQL API | API integrations and CI/CD hooks returning errors |
| Search | Story and epic search returning no results |
| Workflow automation engine | Automated state transitions and actions not triggering |
| Notification delivery | Mention and assignment notifications not sending |
| Roadmap / epics view | Roadmap boards not loading or updating |
GitHub integration failure is highest-severity for engineering teams with automated workflows — it silently breaks the story→PR→state tracking loop that engineers depend on for accurate sprint boards.
Bring Shortcut updates to your team
Follow reported Shortcut status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Eligible first-time customers can start a free trial, no credit card required.
Follow Shortcut incidents with your team
Follow Shortcut and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
FAQ
Is Shortcut down right now?
This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.
How can I get alerts about Shortcut incidents?
Follow reported Shortcut status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Does an operational Shortcut status mean my application is working?
No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.
Browse the service catalog and plans and alert destinations.
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.