Skip to main content
A
agondek1-Visitor
1-Visitor
October 17, 2018
Question

Thing not running error

  • October 17, 2018
  • 1 reply
  • 3578 views

Is there any reason why a Thing would "stop running" randomly on a production server? This server is hands off with respect to development and no services are programmatically creating Things. We have found instances of Things will stop running without apparent cause and will continue in this state until a developer applies a manual restart of the Thing. Any thoughts/comments would be appreciated.

1 reply

P
posipova20-Turquoise
20-Turquoise
October 18, 2018

Are there any subscriptions/timers running on those things? Any errors in the application log?

A
agondek1-VisitorAuthor
1-Visitor
October 18, 2018

Yes we have subscriptions running on the things. No errors relevant to the problem in the error log. With respect to the subscriptions, I think I saw another post that suggested that a subscription may try to run before the Thing is fully compiled. Is that where you are going? If so, do you have a potential work around? I was thinking maybe a Thing (separate from the ones having the problems) that would have a service that ran on Thing start that delayed for a certain number of seconds before enabling the subscriptions on the problem Things.

P
posipova20-Turquoise
20-Turquoise
October 18, 2018

Correct. Would it be possible to test this theory by disabling the subscription to see if the thing will keep running uninterrupted? If it confirms,  placing an appropriate conditional delay should be sufficient.

Terms & ConditionsCookie settingsAccessibility statement