Steps to reproduce:
- Create script item with the default timeout (3s) and the following script:
- Reload the configuration cache and use the Execute Now button to retrieve the value.
- Observe that item is not receiving data and is not receiving the timeout error for a long time (much longer than the defined timeout).
It is expected that timeout specified would be tolerated better and the item would not stay in this "hanged" state for a long period of time.