Hi,
Sometimes, when I run my workflow, I loose the selector of one click button I created and I have the following error:
Not found element with selector = //*[@class='btn__primary--large from__button--floating mercado-button--primary'] at Auteros.Common.Activities.InvokeWorkflow.InvokeWorkflowActivity.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
To fix it, i have to make a new capture of this button.
I plan to schedule my workflow with the agent and I'm not really confident because of this error.
Do you know if there is another way to fix it ?
Thank you.
You should follow this to generate the XPath that deal with dynamic changes in LinkedIn.
Thank you
Hi, LinkedIn change the class name sometimes at the beginning of page loading. I fixed this issue using OR in my selector :
//*[@class='btn__primary--large from__button--floating mercado-button--primary' or 'class_name']
class_name :
class_name represent the new class you see while inspecting of page after the bug. There is a new class name, inspect it and write the name in class_name in the selector.
Hi @soumdiakite182 ,
Thank you for your help.
I confirm that the class_name of my button changed to this value: btn__primary--large from__button--floating
My selector have now this value: "//*[@class='btn__primary--large from__button--floating mercado-button--primary' or 'btn__primary--large from__button--floating']"
But it's seem still not working.
Can't we use another element of auteros studio to take in consideration the change of class_name ?
Thank you.
@soumdiakite182 , my bad!
I didn't use the good syntax.
I changed to this: "//*[@class='btn__primary--large from__button--floating mercado-button--primary' or @class='btn__primary--large from__button--floating']"
It seems to be working now
Thank you.
Okey!