Invoke Workflow File: An item with the samt key has already been added. Key: Delay_1

[SorenB]

Hello

I am getting an error when trying to run the activity “Invoke Workflow File”.

Invoke Workflow File: An item with the same key has already been added. Key: Delay_1

Any ideas as to why this is happening?

[Srini84 (Srinivas Kadamati)]

@SorenB

This was happening when I copy paste the activity previously and now it was converted to Windows

So, work around I can say is that open the xaml in a notepad and search for the Delay_1
There leave for the first search and if you find other then you can place as Delay_2 and so on

and close the xaml and close the main project and open freshly

Hope this may help you

Thanks,
Srini

[Yoichi]

Hi,

The following post will help you.
Basically we need to modify xaml file or replace activity which has error with new one.

Troubleshooting Guide : Conversion from Windows-Legacy project to Windows project

This topic describes troubleshooting guide regarding conversion from Windows-Legacy project to Windows project as of Dec 2023. Hope this helps those who face these problems. 1 Quick Reference by Error Messages, Situation etc. Phase Error message / Situation Reference Open project foobar.xaml: Cannot create unknown type’{clr-Namespace:UiPath.foo.Activities;assembly=UiPath.bar.Activities}ActivityName’. 2.2 Missing Activities package OR 2.3 Missing activity Development Unable to set pro…

After Windows Conversion: "Unable to start execution: An item with the same key has already been added. Key: VisualBasicValue `1_1 "

SOLUTION! Took a while to dig into this, but I found that after converting a project from the Legacy framework to the Windows framework, it would not compile the Main.xaml any longer. Eventually, I found that the “VisualBasicValue1_1" key was being used for 2 different transitions. (In addition, "VisualBasicValue1_2” was also being used twice.) The new Windows framework did not like the fact that two transitions were being assigned the same key. (See below.) All I did to fix it was change one…

Regards,

[THIRU_NANI (NaNi)]

Hey! @SorenB ,

Can you check whether you have duplicate Variable/Arguments inside the Xaml.

The above error will occur when we have the duplicate names.

Check the Duplicate Variables/Arguments might have created

Regards,
NaNi