#Well look at that you pass null there if

1 messages · Page 1 of 1 (latest)

finite socket
#

yes but if i look than in the database. The invitedBy have been updated

#

and if the member leaves the invited user his invites will go negative

lucid turtle
#

<Invite>.inviter is also a getter so if that user isn’t cached it‘ll be null

#

inviterId will always be present though

finite socket
#

but do you know if there is a way to fix it

lucid turtle
#

fetch the user with the inviterId and pass the resolved user to your function instead

finite socket
#

it looks like if it is cached before that it don't work and when it needs to recatch it than it works

lucid turtle
#

Huh? What do you mean by recatch?

finite socket
#

if it needs to take the invites again

#

when there is a new invite added

#

Here i have the first and second time that a user joins with the same invite without any restarts or when there are new invite code's created

📎 az.pdf
lucid turtle
#

Because your code assumes you have only the uses number in your cache. But you add the whole Invite to your cache. And <Invite> < 26 will never be true

finite socket
#

so you say if i change the inv.uses to something big it will be fixed?

image.png