Forced upgrade to Beta causing errors with check activity

[raven]

Instead of having stable community edition I am now being forced to have Beta versions, which are unstable and with errors. So instead of making RPA I am spending time solving errors in old RPA due to the Beta version.

The UiPath.Core.Activities.Check is causing an error after upgrading to Beta. Please correct the error. I spent two hours finding the error and trying to find a solution but found no solution.

[sangeethaneelavannan1 (Sangeetha Neelavannan)]

@raven

The UiPath.Core.Activities.Check is causing an error after upgrading to Beta. Please correct the error. I spent two hours finding the error and trying to find a solution but found no solution.

Hi Raven,
May I know the error which you are facing?

[raven]

[sangeethaneelavannan1 (Sangeetha Neelavannan)]

Your input has a null value and check whether it has a value or not.

Check Activity Error

Hello, I also hit this issue. I got a old script using legacy window mode, It works before convert. But after I converted. the “Check” activity made my script error. After that, I create a new project with one “Check” activity alone. The error still hit. Do anyone know how can I downgrade to previous version?

I think your issue is same as above
Use modern check activity

[raven]

I will try with modern when I get the opportunity, but does this mean that classic activities will provide errors one by one with each update of Studio?

[Leo_Hung]

I always got the similar experence for the enforce beta upgrade. Actually, the aims on using RPA is saving our time. But we used up lot of my time on debugging my old script due with enforce upgrade. for this case, “Check” is a very common activity, Howcome UiPath can disable without any acknowledgement to developer? Due to the grow of the RPA script, the “enfore beta upgrade” is ready a blue sit idea to developer.