Potential Fix for Invocation Errors

[Anonymous]

Note from Michael Lowe @ BP: 
This I not really a problem with wait stages as Blue Prism naturally iterates through the DOM repeatedly looking for the element (for the allotted period of time). However with reads, writes and navigates it will only attempt it once (throwing the classic element not found error if the element doesn’t exist). Possibly having these stages try a couple of times automatically would resolve this issue, but that’s not the way the product works right now. I will raise it as a product suggestion which will get considered for a future development.

This was in response to our continued problems with Invocation errors on Edge/V6.9

[Anonymous]

Great idea Molly, and something we're really struggling with. Thanks for raising.

[KatherineHeason]

Fab idea - let's get it in there and reduce invoke errors.

[AmyTsaousi]

Hi Molly,
Thanks for submitting your idea. Can you please elaborate on the issue you're facing and provide more details on how your idea can could resolve the problems you're facing? Once we have a clearer perspective for your use case, we'll review your idea again. 

Thanks so much,
Amy

[AmyTsaousi]

Hi Molly, 
Thank you for your idea. Unfortunately because we don't understand the context behind your idea we can't proceed with routing it through to next steps in the ideation process. 

As we can see lots of people have liked this idea, please resubmit your idea and include as much detail as to why you'd like us to look into your idea. Then we'll be able to assess it again in the future once it hits enough votes.

All the best,
Amy