If you encounter unexpected step behavior or test results when running tests in Autify Nexus, there are a few ways you can troubleshoot the problem and potentially identify or resolve the issue yourself before contacting our support team.
Analyze the test results
If you are encountering an unexpected step failure, looking carefully at the overall test results is a great place to start. Make sure you look not only at the failing step but also its preceding steps, too. Silent failures or changes in behavior in earlier steps in a scenario can have downstream effects, causing unexpected test results.
The following are different places to check on the test results page that may help you narrow down the issue.
Check the error message
The error reported in the failing step itself may be useful to you. Read it carefully and see if you can find any clues as to why the failure occurred. It may be an issue with Autify Nexus, but it could also be an indicator that something changed on your website since the last time you executed the test.
Example
Take the following Element not found error for example.
.png?sv=2026-02-06&spr=https&st=2026-05-30T11%3A41%3A28Z&se=2026-05-30T11%3A55%3A28Z&sr=c&sp=r&sig=hJc89X9nw1OBkPPqwAv06JMJjQ0c9vPl4inAGqVDo9Y%3D)
The last line shows that Autify Nexus was looking for a locator of an element with the ID :msmx-sheet-APPLICATION-r19:-input-id
But examining the target page shows that the target element now has the following markup.
<input class="slds-input" id=":msmx-sheet-APPLICATION-r5z:-input-id" />The ID has been changed and, based on its structure, appears to be a dynamically-generated ID.
In this case, a good solution would be to update the element’s markup to include a more stable locator, such as adding a data-testid attribute, then re-record or update the step to use the new locator.
Check screenshots
By clicking on the screenshot for a given step, you can see the screenshot of the state of the page during test execution and even compare it to previous successful runs when applicable. There may be some clues in the screenshot as to why a certain behavior is happening.
Example
Take the following text assertion (step 9) as an example.
It’s a text assertion on a toast message that previously passed but has now started to fail.
Based on the screenshot, it’s clear that the toast message is missing from the bottom right of the screen. Did Autify Nexus somehow fail to trigger the toast message as expected?
.png?sv=2026-02-06&spr=https&st=2026-05-30T11%3A41%3A28Z&se=2026-05-30T11%3A55%3A28Z&sr=c&sp=r&sig=hJc89X9nw1OBkPPqwAv06JMJjQ0c9vPl4inAGqVDo9Y%3D)
Looking at previous steps reveals the actual problem.
Screenshots for steps 5 - 7 show that the the toast message was triggered in the bottom right of the page as expected, but it disappeared after 3 seconds.
.png?sv=2026-02-06&spr=https&st=2026-05-30T11%3A41%3A28Z&se=2026-05-30T11%3A55%3A28Z&sr=c&sp=r&sig=hJc89X9nw1OBkPPqwAv06JMJjQ0c9vPl4inAGqVDo9Y%3D)
A solution here would be to increase the toast message’s duration, or decrease the amount of sleep time in the scenario if possible.
Check browser logs
Browser console logs can be accessed by clicking on the colored square(s) to the right of the step.
.png?sv=2026-02-06&spr=https&st=2026-05-30T11%3A41%3A28Z&se=2026-05-30T11%3A55%3A28Z&sr=c&sp=r&sig=hJc89X9nw1OBkPPqwAv06JMJjQ0c9vPl4inAGqVDo9Y%3D)
If your site logs helpful debugging information to the console during development, this is a great place to check and see if anything went wrong.
Example
For example, the ERROR console logs below show that some content was blocked due to a CORS error during test execution.
.png?sv=2026-02-06&spr=https&st=2026-05-30T11%3A41%3A28Z&se=2026-05-30T11%3A55%3A28Z&sr=c&sp=r&sig=hJc89X9nw1OBkPPqwAv06JMJjQ0c9vPl4inAGqVDo9Y%3D)
We can conclude that the step failed because it couldn’t access what it needed during test execution and report the issue to our internal engineering team for further investigation.
Confirm the behavior without using Autify Nexus
It also helps to confirm that your site hasn’t changed since the last time you used it with Autify Nexus.
Testing the actions manually on the target site in a normal browser session can help you determine if the issue only happens when using Autify Nexus.
Check our documentation site
We also encourage you to search through our documentation!
For example, read through relevant articles in the “Autify Nexus features” section to see whether your use case is appropriate. Or check the “Troubleshooting” section and see if your problem has been listed and can be solved or confirmed with known troubleshooting steps.
Change the way you are running the test
Changing how the test is run can sometimes give valuable insight into the problem.
For example:
Changing between local and cloud execution
Changing between headed and headless modes [Local execution] [Cloud execution]
Running the scenario by itself if it is currently running in a group, such as in a test plan or using data
Detaching a shared group step and using local references instead
Change the environment
Depending on the issue, you might also consider trying other environments in which to run your test. That includes:
Changing the browser you’re using for test execution
Changing the network your computer is on if you are running tests locally
Changing the computer itself if you are running tests locally
Use another computer if you have access to one
Ask your co-worker to try the same test or action and see what happens
Contact customer support
Even if you can’t fully resolve the problem by following the above guidelines, you will have gained a clearer idea of the problem and where or why it might be occurring.
When contacting our support team, please send your initial troubleshooting findings along with the other required information as it will help us to more quickly understand and address your problem.