Hi,
Context :
I’ve deployed the following code with all .env variables in place.
Locally same config is able to communicate with LangSmith deployed (plus plan) graph.
Repo link : GitHub - engagepy/LangGraph-Multi-Tool-Agent
Issue :
Hey @engagepy,
Gave your repo a quick scan - from the langgraph.json in it, it looks like you’re trying to deploy an app with LangGraph API endpoints onto Vercel - I don’t think they support this spec.
You’ll need to recreate your own endpoints that wrap your graph if you want to do this, but note that there are some stateful aspects of the API that don’t translate well to serverless environments:
I’d recommend you deploy your backend on platform and call out to your deployment from your Vercel app.
Thanks for responding Jacob,
By deploying on platform do you mean LangSmith ? Because I have.
I tried an EC2 with TMUX, calling both back-end and front-end. Same issue, no responses coming to front-end.
Asia | North America | MEA | UK
Site : ASTRA TECHZ
Disclaimer: The information contained in this communication (including any attachment(s) hereto) is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. If you received this message by mistake, please reply to this message and follow with its deletion, so that such a mistake does not occur in the future. Sender and all entities are not liable for the improper transmission of this communication or for any damages sustained as a result of this communication.
Oh, you are saying your backend is unreachable from your Vercel-hosted frontend?
What is the error you’re seeing?
Just did not connect, so I’ve removed the deployment in all fairness within a week.
Haven’t used it in prod. Looking at alternate deployments while sticking with LangGraph, love it.
Mail trail is to revoke the invoice that is being raised to me for 30$ + approx.
Happy to clear, but in fairness if marked void would help.
Do let me know.
Thanks !
Asia | North America | MEA | UK
Site : ASTRA TECHZ
Disclaimer: The information contained in this communication (including any attachment(s) hereto) is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. If you received this message by mistake, please reply to this message and follow with its deletion, so that such a mistake does not occur in the future. Sender and all entities are not liable for the improper transmission of this communication or for any damages sustained as a result of this communication.
