Skip to main content

In testing an automaton I am building, I noticed that User meta data takes some time to process and update in the API. My use case was around the number of topics, but I’d expect similar things for other data points and fields. 

  1. Using myself as the test case, I did the API call to GET user and saw that I have X topics. 
  2. I posted another topic
  3. I ran the API call again, got the same exact # of topics
    1. Tried again every few minutes with the same experience
    2. It seems to updated in various intervals >30 minutes

I’ve experienced this delay for both types of user calls: 

  • /user/{id} 
  • /user/{field}/{value}

Shoutout to ​@tnelson who highlighted this insight as a pain point in this question: 

 

Hope we can get some realtime data through the API if at all possible. Thanks for following up on this and doing your own testing ​@DannyPancratz 

Hey ​@DannyPancratz - I checked with one of our engineers, who said that while these updates are asynchronous, we wouldn’t expect a delay of more than a few seconds.  Can you let us know which client you’re using?  It’s apparently possible that the client is caching responses.  If we know the client you’re using we can investigate to rule out if something is going on our side.

​@tnelson seems to have tested a lot more than I have. 

But i was testing with Postman and with Zapier. 

​@Kenneth R linking the other thread for visibility.

I’m using Tray.io to hit the Gainsight CC API.
Example flow would be:
- Put request to /user/{userId}/badge/{badgeId} - awarded badge shows up on the site instantly.
- Get request to /user/{userId} - which returns all user info including awarded badges.
The secondary API call does not show the newly awarded badge sometimes for upwards of 30 minutes, despite it being visible on the website instantly.

Hey ​@DannyPancratz and ​@tnelson - our engineers have been digging into this and there is indeed some delay happening (as you describe) - it is on our side and relating to caching.  They’re looking into how that could be improved or fixed.  

Reply


Terms & ConditionsCookie settings