Jump to content
Welcome to our new Citrix community!
  • 0

Inconsistent Results from DaaS Applications API (/Applications)

Jeff Van Note


I noticed I am getting duplicate applications if I don't set a limit of 1000 for this call and missing some other applications visible in DaaS. By duplicate I mean the same name and same ID. The total rows returned is correct.

For example, calling:


, then calling:


,until the continuation token is null will give duplicate values.

If I specify ​a limit of 1000, I don't get any duplicates and can see the missing ones. I've seen this happen with Azure Data Factory and with a Python script created for troubleshooting. We have about 2,400 applications in total. If I use a limit of 250 or specify no limit, I get some duplicates/some missing, but the correct row count.

The general approach we take is make the initial call to the API, check for a continuation token, and then loop, calling with the token returned by each result set until it is null.

Is there an issue with my approach that somehow specifying 1000 resolves?

Link to comment

2 answers to this question

Recommended Posts

  • 0

Addressing inconsistencies in API responses is crucial for ensuring seamless integration with DaaS applications. It is imperative for any android application development company to have a robust understanding of API behavior to deliver a reliable user experience. This issue highlights the importance of thorough testing and continuous monitoring to guarantee consistent performance. Kudos to the team for tackling this challenge head on.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...