I have a SmartApp that runs twice a day. In the morning it runs one process and in the evening it runs a different process. The evening process is a little more involved, but not significantly. Over the last few weeks (especially the past week) I have noticed that the morning process has increased from around 4 seconds to over 20 seconds. The evening process has increased from around 8 seconds to over 20 seconds. The times do not coincide with sunrise or sunset (in the US).
With 20 seconds (or so) being the magic number for ST killing an app, this has become a major problem. The app was not changed so that cannot account for the increase in time. No new devices have been added either. My internet connection is fine - no issues. The issue is not just isolated to my app, but also seems to be affecting the ecobee app as well. It appears that anything that involves cloud-to-cloud or round-trip-to-cloud (i.e. my app checks the status of one device before making a change to another) is slowly increasing in execution time. Maybe this issue will go away with Hub v2 (and likely replaced with some other issue), although ecobee may still be an issue due to its cloud dependence (if I understand correctly how Hub v2 decides whether or not the app runs locally on the hub).
Once the times increase to the point of critical mass, the apps fail. I understand the need to limit execution time, but execution time is dependent on more than just the app. Has anyone else noticed this?