Validation errors - Check App State in Use Application: Excel

Help Activities
, , ,
1

Hello

Since the UiPath upgrade to the StudioX version I get validation errors like this every now and then. The workaround is that I mutate the corresponding activity and reset the customizations afterwards. However, in the long run this is not a good solution, so I wanted to know how I can get rid of the problem completely. Can anyone give me a tip here?

Beim Ausführen der Einschränkung ‘Constraint’ für die Aktivität ‘Check App State’ vom Typ UiPath.UIAutomationNext.Activities.NCheckState ist eine interne Einschränkungsausnahme aufgetreten. Ausnahme: System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.

  • bei System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)*
  • bei System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)*
  • bei System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs)*
  • bei System.Activities.Validation.ActivityValidationServices.Run.Constraints(ChildActivity childActivity, ActivityCallStack parentChain, IList1 constraints, ProcessActivityTreeOptions options, Boolean suppressGetChildrenViolations, IList1& validationErrors)*

Thanks

1 Like
2

Hey @jael.koller

You want to use Check App State inside Use App or Browser ?

Thanks
#nK

3

I would like to use the Check App State in the Use App. When starting Excel there are sometimes popup messages (e.g. read-only etc.) and the check targets those messages.

1 Like
4

Hey @jael.koller

Yes, Why not. You can please use it.

So if you use it you are getting above error from StudioX ?

Thanks
#nK

5

I have already implemented this this way.

The validation error doesn’t always hit, but it hits once in a while, even if I don’t make any changes. This error appears since the StudioX version.

6

Unfortunately, the problem still exists. Another employee also encountered this problem yesterday.