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
I've noticed experimentally that within the device twin callback, delays cause crashes. However, within direct method callback, this seems to not be the case. Is it bad practice to have delays within a direct method callback? For example, waiting on a queue to receive some data.
According to Azure, a direct method response can take up to 300s, but I assumed that you can't have the Direct Method handler have a 5 minute delay inside it.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Delays / waits in Direct Method / Device Twin Callbacks
Delays / waits in Direct Method / Device Twin Callbacks (CA-269)
Jan 18, 2023
I've noticed experimentally that within the device twin callback, delays cause crashes. However, within direct method callback, this seems to not be the case. Is it bad practice to have delays within a direct method callback? For example, waiting on a queue to receive some data.
According to Azure, a direct method response can take up to 300s, but I assumed that you can't have the Direct Method handler have a 5 minute delay inside it.
The text was updated successfully, but these errors were encountered: