Issue Summary:
Test execution failed due to step timeout during execution. This issue typically occurs when a specific test step exceeds the allocated time limit, causing the entire test run to fail.
Solution:
To address this, you can consider increasing the timeout settings for the affected steps. Timeout settings can be applied in two ways. Let's look at them one by one.
Adding Timeout from Run Wizard page
1. Open the Run wizard on your test case. Click the Run Button, select Run on Browser option, the click Local Run.
![](https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/88063267149/original/qd_Us1HRicewRFS-s_L4bBJhGBPXzPFTyg.png?1719321792)
On the Run Wizard page, click to expand the Advanced Settings tab.
![](https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/88063268057/original/p-TSHSQsP61kBFlT7r8mfK6ynta9y_S3lw.png?1719322015)
Set the timeout value in seconds as shown below. You can set any value in seconds. The time added should be enough to let the steps execute sucessfully.
Adding Timeout Value in Execution Agent
On your execution agent, open the tools menu, select Plugin settings and add the timeout value in the respective plugin as shown. Whenever the test case is executed with the plugin, the steps will take the given value before timeout.
For example, test cases executed with Oracle Fusion plugin will have step timeout value of 30 seconds as shown below.
![](https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/88063268762/original/rkcc5sh8EOvStIwrjDzlsLtBskmRQGlwXA.png?1719322202)
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article