Skip to main content
Solved

Cursor has expired error

  • December 12, 2024
  • 4 replies
  • 57 views

Forum|alt.badge.img

When using the calls API to retrieve the records, I received an error code 400 with the error stating ‘cursor has expired’. This happens sometimes and sometimes it doesn’t. What are the possibilities that cause the cursor to expire? Does it have a time limit? 

Best answer by sudharaka-codimite

Hi  ​@Molly Kipnis 


I figured out the problem. I sent the request for the first set of records and got a cursor, and used that cursor an hour after to get the second set of records. So, based on the testing I did, it seems the cursor expires after an hour. 
 

Thank you for getting back to me.

View original
Did this topic help you find an answer to your question?

4 replies

Molly Kipnis
Forum|alt.badge.img+2
  • Community Manager
  • 597 replies
  • December 12, 2024

Hey ​@sudharaka-codimite, checking on this for you! Stay tuned :) 


Molly Kipnis
Forum|alt.badge.img+2
  • Community Manager
  • 597 replies
  • December 16, 2024

Hi again ​@sudharaka-codimite!

Is it possible that you aren’t updating the cursor field with the value provided in your previous call? (Meaning that if the results are greater than what can be returned with one call, you’ll need to make the same call again with the cursor value provided in the previous return to retrieve the next set of results to fulfill the original request.)

If this isn’t the case, I’d recommend filling out the developer API support form so that our team can help troubleshoot this. 

I hope this helps!


Forum|alt.badge.img

Hi  ​@Molly Kipnis 


I figured out the problem. I sent the request for the first set of records and got a cursor, and used that cursor an hour after to get the second set of records. So, based on the testing I did, it seems the cursor expires after an hour. 
 

Thank you for getting back to me.


Molly Kipnis
Forum|alt.badge.img+2
  • Community Manager
  • 597 replies
  • December 20, 2024

Glad you figured it out! Thanks for following up! ​@sudharaka-codimite 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
×