HI Jason,
I would suggest trying to substitute the ticket for a user token. They are a newer option that I have found to be a bit more robust when being used in APIs and they have some more advanced security features. They also do not expire under the same time table as authorization tickets. I have included linked below our help topic on user tokens. I would suggest trying to just adjust your API call that way.
https://help.quickbase.com/api-guide/create_user_tokens.htmlThere isn't an API issue I am familiar with that would cause an API like that to not fire unless the ticket itself was bad or expired, but in that instance it shouldn't suddenly work when you clear your cache. If after you make the change to a user token this issue still persists at that point I would suggest putting in a support case to work with a Care Team member so they can see the specifics of your set up and that error message and look at it more closely with you.