API query parameter "limit" not working anymore?

API & integrations
1

Hi,

I am using the Tracker Debugger API to access the stream of sessions with a defined limit=1 in the URL but I (now) sometimes get a bunch of sessions in the response. Is this a known problem? As I did not change anything in my code that uses to work as expected a few weeks ago.

Changing the value leads to odd results. Queries with limit=2 can result in 4 sessions, changing the value back to 1 then occasionally works. Very strange. Is that a general problem or am I the only one experiencing such results?

best,
Markus

2

Hi @mbaersch,
Could you share the request content that you are sending to the debugger endpoint?

3

Hi,

there is no payload beyond the auth header and the parameters in the request URL to the following endpoint:

/api/tracker/v1/debugger?app_id=xxx&lookup_window=300&limit=1&event_type=8

Which led to the results described above yesterday. Can still reproduce the problem here myself today. Example:

image
image844×470 23.5 KB

When I change the value for “limit” a few times and run the same request again, I will get the desired number of results at some point but it seems totally random when it works or does not :frowning:

best,
Markus

4

Do you use User ID for these sessions?

5

Yes, that’s the case

6

Generally, it is more a thing than a bug. Can you tell me more about your use case?

7

the request serves to see if there are any sessions with a specific event (the event type used just is an example) and the next block does not expect more than one line as a result.

As it is easy to fix I still would expect the parameter to work as it did and as it is documented, no matter what use case(?)

8

Hi Markus,

We’ll introduce a fix for this with the next update.

9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.