langchain-ai/langgraph
1
0
Fork 0
mirror of https://github.com/langchain-ai/langgraph.git synced 2026-07-15 12:35:43 -04:00
Code Issues 314 Packages Projects Releases 17 Wiki Activity

LangGraph Platform Cloud SaaS timing out on deployments #452

New Issue
Closed
opened 2026-02-20 17:40:13 -05:00 by yindo · 4 comments
yindo commented 2026-02-20 17:40:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @austinberke on GitHub (Feb 11, 2025).

Checked other resources

  • This is a bug, not a usage question. For questions, please use GitHub Discussions.
  • I added a clear and detailed title that summarizes the issue.
  • I read what a minimal reproducible example is (https://stackoverflow.com/help/minimal-reproducible-example).
  • I included a self-contained, minimal example that demonstrates the issue INCLUDING all the relevant imports. The code run AS IS to reproduce the issue.

Example Code

Steps to reproduce: 
1. Push to branch in connected repo
2. Revision + build is automatically kicked off in LangGraph Platform
3. Wait for "Building", "Waiting for Deploy", "Deploying LangGraph Server" messages
4. The deploy will take a few minutes - if it goes over 5 minutes it will time out and fail

Error Message and Stack Trace (if applicable)

Timeout: Deployment is not ready after 300 seconds.

Description

I've been trying to set up LangGraph Platform Cloud SaaS to evaluate if it's stable enough for us to host on, and although the first couple deployments worked fine, the past several ones have failed with the following error message:

Timeout: Deployment is not ready after 300 seconds.

Some of these deployments will show server logs that it did successfully start up after showing the failure message, but many of them have empty server logs.

Is it normal for deployments to be taking this long? Was there an outage today? If it regularly goes over 300 sec should this timeout be increased?

System Info

n/a

Originally created by @austinberke on GitHub (Feb 11, 2025). ### Checked other resources - [x] This is a bug, not a usage question. For questions, please use GitHub Discussions. - [x] I added a clear and detailed title that summarizes the issue. - [x] I read what a minimal reproducible example is (https://stackoverflow.com/help/minimal-reproducible-example). - [x] I included a self-contained, minimal example that demonstrates the issue INCLUDING all the relevant imports. The code run AS IS to reproduce the issue. ### Example Code ```python Steps to reproduce: 1. Push to branch in connected repo 2. Revision + build is automatically kicked off in LangGraph Platform 3. Wait for "Building", "Waiting for Deploy", "Deploying LangGraph Server" messages 4. The deploy will take a few minutes - if it goes over 5 minutes it will time out and fail ``` ### Error Message and Stack Trace (if applicable) ```shell Timeout: Deployment is not ready after 300 seconds. ``` ### Description I've been trying to set up LangGraph Platform Cloud SaaS to evaluate if it's stable enough for us to host on, and although the first couple deployments worked fine, the past several ones have failed with the following error message: Timeout: Deployment is not ready after 300 seconds. Some of these deployments will show server logs that it did successfully start up after showing the failure message, but many of them have empty server logs. Is it normal for deployments to be taking this long? Was there an outage today? If it regularly goes over 300 sec should this timeout be increased? ### System Info n/a
yindo closed this issue 2026-02-20 17:40:13 -05:00
yindo commented 2026-02-20 17:40:13 -05:00
Author
Owner
Copy Link
Copy Source

@hinthornw commented on GitHub (Feb 11, 2025):

cc @andrewnguonly

@hinthornw commented on GitHub (Feb 11, 2025): cc @andrewnguonly
yindo commented 2026-02-20 17:40:13 -05:00
Author
Owner
Copy Link
Copy Source

@andrewnguonly commented on GitHub (Feb 11, 2025):

Is it normal for deployments to be taking this long?

No

Was there an outage today?

There was a short outage today that has since been resolved.

If it regularly goes over 300 sec should this timeout be increased?

It doesn't regularly go over 300 seconds.

What's the revision ID of the deployment? I can help debug the issue.

@andrewnguonly commented on GitHub (Feb 11, 2025): > Is it normal for deployments to be taking this long? No > Was there an outage today? There was a short outage today that has since been resolved. > If it regularly goes over 300 sec should this timeout be increased? It doesn't regularly go over 300 seconds. --- What's the revision ID of the deployment? I can help debug the issue.
yindo commented 2026-02-20 17:40:13 -05:00
Author
Owner
Copy Link
Copy Source

@austinberke commented on GitHub (Feb 11, 2025):

Responded via email with revision ID. Thank you for the quick confirmation of an outage.

@austinberke commented on GitHub (Feb 11, 2025): Responded via email with revision ID. Thank you for the quick confirmation of an outage.
yindo commented 2026-02-20 17:40:13 -05:00
Author
Owner
Copy Link
Copy Source

@cadence-day-dev commented on GitHub (Mar 19, 2025):

I am currently getting the same error "Timeout: Deployment is not ready after 300 seconds.". Is there an outage at the moment?

However, in the Server log, I have an error saying "Redis ping failed". Then, I get a couple of "[INFO] HTTP Request: POST https://eu.api.smith.langchain.com/v1/metadata/submit "HTTP/1.1 204 No Content"" and Sweeped runs

The revision ID is 85700ba2-cf58-4c3d-ac44-096a256bb70e.

Error fixed. Sorry. It was because unit-tests were failing for linting errors.

@cadence-day-dev commented on GitHub (Mar 19, 2025): I am currently getting the same error "Timeout: Deployment is not ready after 300 seconds.". Is there an outage at the moment? However, in the Server log, I have an error saying "Redis ping failed". Then, I get a couple of "[INFO] HTTP Request: POST https://eu.api.smith.langchain.com/v1/metadata/submit "HTTP/1.1 204 No Content"" and Sweeped runs The revision ID is 85700ba2-cf58-4c3d-ac44-096a256bb70e. **Error fixed. Sorry. It was because unit-tests were failing for linting errors.**
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agents
awaiting author revision
bug
change
chat models
checkpointer
ci
code quality
code quality
dependencies
documentation
drawing
duplicate
enhancement
good first issue
help wanted
invalid
maintainer
meta
missing information
not maintained by langchain
open-swe-auto
open-swe-max
open-swe-max-auto
pending
performance
pull-request
Mirrored from GitHub Pull Request
 question
requires design
sdk
server
stale
studio
tests
type checking
usage question
v0.5
v1.1
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraph#452
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?