You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We recently observed that the sensor tasks are stuck in running state for more than 2 days. the primary reason for this behaviour is that the timeout is not configured in the get request here
To Reproduce
Steps to reproduce the behavior:
There are no fix steps to reproduce this issue, as rarely the request gets stuck, but as per the python request library documention its recommended to always add timout in all requests, here is the reference
Expected behavior
After configuring the SENSOR_DEFAULT_TIMEOUT_IN_SECS variable, the sensor request should get timeout and next run should get scheduled
The text was updated successfully, but these errors were encountered:
Describe the bug
We recently observed that the sensor tasks are stuck in running state for more than 2 days. the primary reason for this behaviour is that the timeout is not configured in the get request here
To Reproduce
Steps to reproduce the behavior:
There are no fix steps to reproduce this issue, as rarely the request gets stuck, but as per the python request library documention its recommended to always add timout in all requests, here is the reference
Expected behavior
After configuring the SENSOR_DEFAULT_TIMEOUT_IN_SECS variable, the sensor request should get timeout and next run should get scheduled
The text was updated successfully, but these errors were encountered: