​
Edge Cases

By default, Simplex fails if the agent cannot find an element on the page. Often, the same flow on different customer accounts will have different elements on the page. This could range from an informational banner (i.e., the customer needs to update their settings on a particular page) to “Accept cookies” popups. This can lead to unexpected behavior with Simplex’s web agents. We recommend you test your workflows with multiple accounts from different customers if you’re automating a specific web page. Simplex has a few tools to help you handle these edge cases.
  • exists: Check if an element exists on the page.
  • scroll: Scroll by a dedicated pixel amount. Can help mitigate differences due to banner popups.
  • get_dropdown_options: Get the text of all the options in a dropdown. Can be useful to match against a list in your internal databases if you need fuzzy matching.
  • get_page_url: Get the current page URL. Can be useful if you know a page might redirect or is dynamic.

​
Evals

We heavily recommend that you run simple evals to ensure that your workflows work as expected at production scale. We’ve provided a simple eval script (in Python) in the following gist: https://gist.github.com/mnocito/aaba43096b3633be7918cb95d3d7d302. We’ve set the default number of runs to 25, but recommend you run up to 100 concurrently.