+1 am getting request timeouts this morning
# report-bugs
a
+1 am getting request timeouts this morning
โœ… 1
๐Ÿ‘ 2
p
(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using
gt feedback --with-debug-context <any message>
a
i'm just trying to run
gt sync
logs:
Copy code
2026-04-06T14:13:36.605Z: Requesting: {
  "apiServer": "<https://api.graphite.dev/v1>",
  "route": {
    "method": "POST",
    "url": "/graphite/cli/pull-request-info",
    "params": {},
    "response": {}
  },
  "params": {
    "repoOwner": "Miter-HR",
    "repoName": "miter",
    "prNumbers": [
      21837,
      21550,
      21551,
      21552,
      21183,
      21184,
      21748,
      21974,
      21925,
      21883,
      21896,
      21314,
      21932,
      21978,
      21449,
      21310,
      21800,
      21746,
      21747,
      21799,
      21907,
      21946,
      21937,
      21911,
      21780,
      21795,
      21912
    ],
    "prHeadRefNames": [
      "anish/fie-2819-dual-pane-picker-font-standardization",
      "anish/fie-2824-2816-formsv2-value-format-fix",
      "anish/fix-safety-meeting-cross-company-leak",
      "anish/pylon-mcp-server"
    ],
    "trunkBranchNames": [
      "main"
    ],
    "consistent": true,
    "callsite": "newSyncAction"
  }
}
2026-04-06T14:14:36.609Z: Request timed out, retrying #0: {
  "errorMessage": "Request timed out after 60000 ms",
  "errorCause": "Unknown cause"
}
2026-04-06T14:15:36.713Z: Request timed out, retrying #1: {
  "errorMessage": "Request timed out after 60000 ms",
  "errorCause": "Unknown cause"
}
j
This is my exact issue
๐Ÿ‘ 1
I also had some colleagues try it as well and they are also experiencing the same thing
a
yeah, usually when this happens it's bc github is down
but this time it's very obviously graphite's API
looks like they've posted a status update
j
yeah - that was the first thing I checked. I tried a github pull and that worked
nice - a minute ago it wasn't there ๐Ÿ˜›
a
+1
so much for starting 13 min ago ๐Ÿ˜‚
๐Ÿซ  1
is there a blessed workaround when gt is down to keep making progress on stacks?
j
that's a great question - I think you have to rebase manually ๐Ÿ˜ญ
๐Ÿ˜ญ 1
one branch at a time
๐Ÿ‘ 1
a
figured that was the answer..just was hoping there was something better
j
What's funny about that status update is that it has only identified Slack Notifications as being an issue. It says GitHub is fully operational. thinking
w
Well, it says GitHub is operational because that's GitHub
But the Dashboard and CLI both have red X's in your screenshot
j
yes - I understand ๐Ÿ˜‰
w
๐Ÿ‘ That understanding wasn't evident from the last message. Glad you got it though! ๐Ÿ™‚ Hopefully we'll be back soon.
p
We're working on it, so sorry!
๐Ÿงก 5
a
any ETA?
p
This incident has been resolved and we've updated the status page accordingly. Apologies again for any inconvenience this caused. -- Graphite Support graphite.com