You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Close the browser tab while the job is still running.
Reopen a tab using the permalink to the job you where provided just now.
✔️ Expected Behavior
The link should display the job currently running in the WebApp page, displaying the progress and the log, with the options to pause/stop/restart the job.
❌ Actual Behavior
The WebApps permalink provided don't point to the current workflow job running, but shows a new job start page. No configuration input is preserved. Recovering a job running is impossible once you close the browser tab.
If you try to start a new job, it would answer with: Please wait for the response to the previous message to complete.
But the user have no way to see the queue of jobs running, nor to stop/pause them or get the logs or the results.
Money is spent without any option for the user to manage the running jobs or stopping them if they are consuming too much tokens.
The text was updated successfully, but these errors were encountered:
To address the issue of WebApps links not pointing to the current workflow running, you can use the handleBackupDraft and handleLoadBackupDraft functions from the useWorkflowRun hook. These functions help preserve and restore the workflow state, allowing job recovery after closing the browser tab.
Steps to Implement:
Backup the Current Workflow State:
Use handleBackupDraft to save the current state of the workflow, including nodes, edges, viewport, features, and environment variables.
These steps ensure that the workflow state is preserved and can be restored, allowing for job recovery after closing and reopening the browser tab [1][2].
crazywoola
changed the title
[BUG] WebApps links don't point to the current workflow running. Recovering a job running is impossible once you close the browser tab.
WebApps links don't point to the current workflow running. Recovering a job running is impossible once you close the browser tab.
Oct 10, 2024
Self Checks
Dify version
0.9.1
Cloud or Self Hosted
Cloud
Steps to reproduce
✔️ Expected Behavior
The link should display the job currently running in the WebApp page, displaying the progress and the log, with the options to pause/stop/restart the job.
❌ Actual Behavior
The WebApps permalink provided don't point to the current workflow job running, but shows a new job start page. No configuration input is preserved. Recovering a job running is impossible once you close the browser tab.
If you try to start a new job, it would answer with:
Please wait for the response to the previous message to complete.
But the user have no way to see the queue of jobs running, nor to stop/pause them or get the logs or the results.
Money is spent without any option for the user to manage the running jobs or stopping them if they are consuming too much tokens.
The text was updated successfully, but these errors were encountered: