[Bug]: Workflow 'twoagents' is not among the defined enum values. about autogen HOT 10 OPEN

Hi @RafalSebastian ,

Work is being done to improve migration of data across versions, but not yet supported so workflows from previous versions will not be compatible with v 0.1.0 +.

With respect to multiple agents, the way to do that is to.

• Under agents, create a new agent, select group chat, click create. Once this is created, you should see an agents tab. This should then let you add agents to the group chat. Finally, add a model to your group chat.
• Under workflow, select your user proxy as sender and then your group chat agent as receiver.

from autogen.

Any chance you can share the command line log that shows up when this error occurs? This will be helpful in debugging the issuel.
Eitherway, I'd recommend a fresh conda environment just to ensure there are no conflicts (e.g., version conflicts) and specify a new appdir (ensure the right version of the db is created).

from autogen.

Victor, the issue appears when trying to upload the previous version workflow json to the latest version of AutoGenStudio. As you said, it won't work and now I know why. Additionally it helped to create fresh conda env and new appdir (which wasn't necessary for clean installation).
New ui logic is far more better and "logical".
Thank you for your support Victor, very much appreciated.

from autogen.

A note to whoever comes after this. With the new version, you have to just start from scratch with everything. You cannot bring any agents, any environments, any workflows from your old project files.

You must start from scratch. For me, this entailed creating an entirely new Docker container and building the backend of my application from scratch which was really annoying.

I was able to save the prompts from my old agents but nothing else, there are errors all the way down - this database error was just the beginning. That's the only solution, good luck!

from autogen.

Hi @TheAmazingRoderic ,

This error is due to an update in the db schema with v 0.1.0 +.
You can correct this by either deleting your current db, or running autogenstudio and pointing it to a new app folder

autogenstudio ui --appdir /path/to/folder

This will create a new db in the /path/to/folder using the right schema.

See docs FAQ on how to specify directory https://microsoft.github.io/autogen/docs/autogen-studio/faqs#q-how-do-i-specify-the-directory-where-fileseg-database-are-stored

from autogen.

Thank you @victordibia, I was able to repair the database. I reported because I believe it is a bug not to have the same validation/constraint of the schema applied on upload/insert into the database to prevent the situation.

from autogen.

I do see the TBD in the typescript:

It seems it would be nice to catch this in back at the the DBManager.upcert

from autogen.

I have created new db with --appdir instruction, and it allowed me to create one Workflow, but could assign only two agents (proxy and assistant). After that, ALL workflows gone.

from autogen.

Thank you Victor for the update. I do not worry much about the issues with migration of data across versions. The problem is I can't define any agent.

same for WIN and LINUX
I will carry experiments on previous versions until this issue is fixed. I do strongly regret that I can't contributre much but I truly appreciate everyones effort to make this project better.

from autogen.

A note to whoever comes after this. With the new version, you have to just start from scratch with everything. You cannot bring any agents, any environments, any workflows from your old project files.

You must start from scratch. For me, this entailed creating an entirely new Docker container and building the backend of my application from scratch which was really annoying.

I was able to save the prompts from my old agents but nothing else, there are errors all the way down - this database error was just the beginning. That's the only solution, good luck!

I have eventually figured it out. , thank you!

from autogen.