hey all- we first set up growthbook in our django ...
# ask-questions
f
hey all- we first set up growthbook in our django app (using the middleware instructions here) about a year ago and ran several experiments without issue. it’d been a while, but we released a new experiment a few weeks ago and over the next few days, we saw the tracking callback get fired a TON of times (it’s now down to an expected level). upon digging in, it looks like the tracking callback got fired almost 3K times per user who got the experiment. any idea what could cause this? thanks!
w
Yikes that is quite a lot and unexpected. Nothing comes to mind within the Growthbook framework that could have caused this. Here are some things you might want to investigate: 1. Did this problem go away all of a sudden? Did it match a deploy time? 2. Was your site maybe DDOSed at that time? 3. Were calls to other endpoints on your site by those users also hit many times? 4. What version of the sdk are you on - you might want to upgrade to the latest? 5. Was there something in your code base that could have caused
is_on
is_off
or
get_feature_value
to fire thousands of times per user? Perhaps an infinite loop that then got timed out after 60s which happen to be able to run about 3k times during that amount of time?
f
thanks for the ideas james! continued to dig in based on the investigations you suggested and saw that the issue was basically option 5- we had a bug in our code that was causing a task to fail and retry thousands of times per user, which caused
get_feature_value
to fire thousands of times per user.
w
Glad you figured it out.