"Received local request for App 4601 that does not exist, path: /trigger from unknown"
Any ideas on how I can clean this up
The easiest way I know of is to restore an old backup from before when you received that error. Then determine what app 4601 is and disconnect it from whatever cloud resource is authorized to use it. Then restore a more recent backup.
Pretty sure that would involve a (non-existent) Rule being called through RM's "local/cloud endpoint" trigger mechanism:
'''https://cloud.hubitat.com/api/...apps/624/trigger?access_token='''
Have you removed or disabled any Rules lately?
Here are some of the customary Log entries corresponding with (a) successful triggering of an enabled rule's endpoint, (b) unsuccessful attempt to trigger same rule while disabled, and (c) system message when attempting to trigger same rule after it has been deleted.
Won't help now, but you might find this useful going forward: