HomeRunner works best with its own Guesty API client rather than one shared with other tools.
Why this happens. Guesty limits each API client to 5 access-token issuances per day, on a rolling 24-hour window. When HomeRunner shares a client with other tools, all of their token requests count against the same quota. If the combined usage uses up the limit, Guesty blocks new tokens for every tool on that client, including HomeRunner, and syncing stops.
What you can do. Give HomeRunner a dedicated Guesty API client. This keeps HomeRunner’s token usage within its own quota, so other integrations do not affect it.