-
Notifications
You must be signed in to change notification settings - Fork 4k
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
in 1.0.14 URGENT : Langflow Front end times out while saving, deletes current workflow #3164
Comments
To address the issue in Langflow version 1.0.14 on Ubuntu 22.04 with Python 3.10, where the front end times out during a save or cancel save operation, causing the current workflow to show no components and eventually leading to the flow being deleted after logging off and logging in again, you can try the following steps:
Here is an example of how you might increase the timeout settings in a typical frontend configuration: // Example of increasing timeout settings in an Axios instance
import axios from 'axios';
const axiosInstance = axios.create({
baseURL: 'http://localhost:3000/api/v1',
timeout: 60000, // Set timeout to 60 seconds
headers: {
'Content-Type': 'application/json',
},
});
export default axiosInstance; If the issue persists after trying these steps, you may need to provide more detailed logs or additional context to further diagnose the problem. |
hi @Arron-Clague |
Hi : I think its a DB migration error : 2024-08-05 08:47:54 - ERROR - service - Error migrating transactions service.py:221 |
so : ive backed up my flows via Export all : stopped Langflow, and deleted langflow.db and, re- run create superuser, and still the DB is giving errors : it is still getting corrupt data from somewhere : looks like it from outdated custom components : langflow superuser |
I had this same issue yesterday and lose my entire flow. It seems that my flow components' are taking longer than normal to load, and if you do anything that trigger the auto save, the flow will be saved as an empty canvas. I will try to reproduce in a video later today. |
@appks : Its not a complete solution, but while this gets resolved, backing up the flows via export, deleting langflow.db, and restarting with a new superuser account did get me back running again after re-importing the flows. There are still errors in the DB (as above) but I haven't lost any flows, and the load time issue has gone. |
I think this was solved for the version on 'main' Here's how I could reproduce this bug on my 1.0.14 version (dockerized install) 2024-08-07.18-43-05.mp4However, I noticed that the there's a new loading on the version I cloned today, directly from main. Not sure if it's really fixed now, but it seems worth to share; |
For me, the issue happens mostly with the flows that has the load time issue as Arron said. I've tried to break other flows that load more fast and could not break any of them. If the flow takes some secs to load, messing the canvas around will delete the flow. |
Fixed in the last version! Feel free to test it and open this issue if you find anything wrong! Thanks for the feedback. |
Bug Description
When the front times out, for example with a save or cancel save, the current workflow is show no components. Logging off and logging in again deletes the flow entirely !
Reproduction
Duplicate an existing flow for safety.
Open the flow
Allow the front end to timeout or save to fail
restart
navigate back to collectoion
navigate to flow : flow is empty
navigate back to collection
Flow is now deleted
Expected behavior
To save correctly and not delete user flows.
Who can help?
@ogabrielluiz
@nicoloboschi
@zzzming
@jordanrfrazier
@mfortman11
@NadirJ
Operating System
Ubuntu 22.04
Langflow Version
1.0.14
Python Version
3.10
Screenshot
No response
Flow File
No response
The text was updated successfully, but these errors were encountered: