I actually ran into this exact same issue with a c...
# office-hours
y
I actually ran into this exact same issue with a client project recently - it’s a pretty common OAuth sync bug with Vapi’s Google integrations. I managed to figure out a few workarounds that got it working properly. If you’re still stuck with it and need it resolved quickly, feel free to DM me. I’ve got some experience troubleshooting Vapi integrations and could probably get this sorted for you pretty fast. Sometimes it’s just a simple browser cache issue, but there are a few other technical things to check on the backend that usually do the trick. Happy to help out if you need it
3 Views