SYS:1 Warning App Does not Exist

My C4 hub is reporting these warnings. How can remove the warning?

sys:12025-12-30 07:08:50.930 PM

warn

Received cloud request for App 129 that does not exist, path: /device/78 from 3.236.131.106

sys:12025-12-30 02:55:51.134 PM

warn

Received cloud request for App 129 that does not exist, path: /device/78 from 44.214.109.37

sys:12024-12-29 11:04:25.678 PM

warn

Received cloud request for App 129 that does not exist, path: /device/78 from 52.90.87.6

sys:12024-12-29 10:56:07.421 PM

warn

Received cloud request for App 129 that does not exist, path: /device/78 from 34.236.36.120

sys:12024-12-29 10:54:26.324 PM

warn

Received cloud request for App 129 that does not exist, path: /device/78 from 3.228.18.148

sys:12024-12-29 06:06:14.391 PM

warn

Received cloud request for App 129 that does not exist, path: /device/78 from 3.235.0.154

sys:12024-12-29 06:05:10.794 PM

warn

Received cloud request for App 129 that does not exist, path: /device/78 from 98.84.45.195

The only way to get rid of the warnings is either to put the app back or tell the sending site to stop. All of IPs that you have listed above are from Amazon.com if that helps.

3 Likes

This generally means that you setup some kind of integration with an external, cloud-connected service, but deleted the relevant app on your hub without also removing the connection from the external service’s end of things.

In other words, something is trying to reach your hub from the cloud, but the hub no longer has any idea what it is.

1 Like

Thanks I'll check the Amazon account and see if I can find it. If I can't figure out what cloud app is causing this and I don't know what App is missing to re-install how can I get rid of this warning?

Restore a database backup that precedes when this warning started. That database will have app 129. And then you figure out which cloud integration to turn off on the cloud service side.

I don't think that will help. Lots of cloud services use AWS, leading to "hits" that come from Amazon IP addresses.

1 Like

What if I don't have a backup that goes that far back?

Then you have to rely on your memory to identify every cloud integration that you had installed.

2 Likes

I've never asked for it here but it would be great if the Hub could somehow store a history of all app IDs and device IDs in a log for situations like this.

Would be easy enough to write a small app - just need to regularly grab the output from
/hub2/devicesList and /hub2/appsList, and then mark up the differences as they occur. Might be a fun exercise for tomorrow if I have time. :sunglasses:

4 Likes

Easy for YOU!!!!! haha It seems we get a similar post to this a couple of times/month. I know that I have been a victim of that error message with no idea the culprit.

1 Like

Me too.
Fortunately I had a DB backup that went back far enough to find the culprit.
I always keep an old backup (approx 3 - 4 months old) just in case I need to go back and dig something up.

2 Likes

You may also be in luck if you use HPM, but have deleted the app outside of that.

It will still show as an installed app in HPM where you can then do a repair and a proper uninstall.

3 Likes

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.