Closed ghost closed 3 years ago
As you can see, the gend command was executed yesterday and the embed timestamp says ended today, yesterday happens the same.
I assume you used mongos cloud cluster so it should be irrelevant, but just to confirm, where do you host your bot?
I assume you used mongos cloud cluster so it should be irrelevant, but just to confirm, where do you host your bot?
on replit
local stored data on replit does not really work, so as far as I know quick.db included. We had such "giveaway resets on it's own" problems before because of that.
But the weird thing is that you said it happend with mongoDB too, which should not be possible since it's in the cloud.
Are you sure you used new GiveawaysManagerWithOwnDatabase
to create your manager? (I just mean if you really used your extended class)
local stored data on replit does not really work, so as far as I know quick.db included. We had such "giveaway resets on it's own" problems before because of that. But the weird thing is that you said it happend with mongoDB too, which should not be possible since it's in the cloud. Are you sure you used
new GiveawaysManagerWithOwnDatabase
to create your manager? (I just mean if you really used your extended class)
Anyway thanks, i thin i did something wrong with mongo, im gonna close issue
Describe the bug
A clear and concise description of what the bug is. When I end a giveaway with the Giveaway End Command or when a giveaway is ended. It will start again for the reaming countdown when ending it after 1-2 hours and says new winners to the cooldown end Error
A screenshot or the text block of the error if there is one.
To Reproduce
Start a giveaway for duration +1day or end one Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen. It will stop the giveaway and not starting more Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
discord-giveaways
version: Lastest 4.5.1discord.js
version: Lastest 12^Add any other context about the problem here.