Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not getting response from langflow API #1320

Closed
sampratha28 opened this issue Jan 11, 2024 · 4 comments
Closed

Not getting response from langflow API #1320

sampratha28 opened this issue Jan 11, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@sampratha28
Copy link

I am not able to get response from the API if the time taken to built the flow is long.

The response has been recieved by the LLM, but not returned by the API.

Copy link

dosubot bot commented Jan 11, 2024

🤖

Hello @sampratha28! I'm Dosu, an assistant bot here to help you out. While we wait for a human maintainer to join us, I'm at your service to help solve bugs, answer questions, and guide you on your journey to become an even more awesome contributor. Let's make your experience with Langflow as frictionless as possible!

Based on the information provided, it seems like you're experiencing a timeout issue when the time taken to build the flow is long. This could be due to the default timeout settings of the langflow API or the server where it's hosted. Unfortunately, I wasn't able to find specific information about the default timeout settings within the langflow repository.

The langflow API uses Celery to handle long-running tasks. When a task takes a long time to complete, it's launched asynchronously using the delay method. The task's ID and an AsyncResult object are returned immediately, and the status of the task can be checked using the get_task method with the task ID. This is designed to prevent the API from blocking while waiting for a long-running task to complete.

If you're not receiving a response from the API, it could be due to an error occurring during the execution of the task. The API is designed to return specific HTTP status codes and error messages depending on the type of error that occurred. For example, if the API key is invalid, a 401 Unauthorized status code is returned. If the flow ID is not found or has no data, a 404 Not Found status code is returned. For other exceptions, a 500 Internal Server Error status code is returned.

To help diagnose the issue, could you please provide the exact error message or status code you're receiving when the API does not respond? Also, could you provide more details about the flow you're trying to build and how long it typically takes? This information will help us understand the issue better and provide a more accurate solution.

For more information, you can refer to the langflow API endpoints and the Celery backend implementation in the langflow repository.

I hope this helps! If you have any more questions or need further clarification, feel free to ask.

Best,
Dosu

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot dosubot bot added the bug Something isn't working label Jan 11, 2024
@sampratha28
Copy link
Author

@dosu-bot. the flow takes typically 6 mins to build

Copy link

dosubot bot commented Jan 11, 2024

🤖

It sounds like you're referring to a specific flow within a software project. If you need assistance with optimizing the build process or any other technical aspect, feel free to provide more details, and I'll be happy to help!


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@anovazzi1
Copy link
Contributor

can you provide the flow for debugging ?

@dosubot dosubot bot added the stale label Jun 20, 2024
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2024
@dosubot dosubot bot removed the stale label Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants