500 Error when the watch timer runs out

[must]

It would be better to add a warning for watch timeout running out (both in the actual response and the connect interface)

[loreanvictor]

@must could not replicate. could you elaborate more on replication scenario?

[must]

I had it when my logic took more time to execute than the set limit for the interface watch tool. I will try to replicate it with a simple logic and see if it triggers the same reaction.

[must]

https://mustsbucket.s3-eu-central-1.amazonaws.com/Screen-Shot-2019-02-24-at-10.13.12-PM.png
https://mustsbucket.s3-eu-central-1.amazonaws.com/Screen-Shot-2019-02-24-at-10.13.04-PM.png
https://mustsbucket.s3-eu-central-1.amazonaws.com/Screen-Shot-2019-02-24-at-10.13.08-PM.png

I just tried it again, and in the latest version, it seems like the time limit is not followed. Please do let me know if I'm missing something here.