#Storage Mode Does Not Save

1 messages · Page 1 of 1 (latest)

topaz shore
#

I have been redirected here from my ticket. My ticket helper and myself are both experiencing this issue. When you enable the "Storage Mode", the setting does not get saved and upon reload or synchronisation, the setting will be disabled again.

static umbra
#

//bug confirmed, even using a different browser doesn't help

#

After saving the settings:

#

After refreshing the page

fleet orbit
#

Idk what ya'll are talking about, it works just fine.
||I've found and fixed the bug =)||

topaz shore
#

🙂

#

Awesome

#

Thank you for the quick response

#

@fleet orbitHey, sorry for the mention. Not sure whether this is related or an error on my end but when I "delete" a ticket, it moves to the correct category and is brought back accordingly. However, when I close the ticket it brought back, I don't get any options to "delete" it again. It just remains there.

topaz shore
#

I can close it just fine

fleet orbit
#

Oh, I see..

topaz shore
#

No other options tho

fleet orbit
#

Storage mode

topaz shore
#

Yes but the channel remains in the original category, not the storage category after I close it again after bringing it back

fleet orbit
#

lets run over the is:
Storage Mode Enabled. <store category>

-> Create Ticket <create category>
-> Delete Ticket <store category> (should be cleared of all messages)
-> Create Ticket pull from <store category> put into <create category>

#

are we correct upto this point?

topaz shore
#

Yes:

I create a ticket
I close a ticket
I delete a ticket (ticket gets moved to storage)

I open a new ticket (ticket is brought back from storage)
I close this ticket and have no options to "delete" it nor does it remove it's overwrite or messages.

fleet orbit
topaz shore
#

The bot has admin

fleet orbit
#

Then it's not that lol

topaz shore
#

lmao

#

As I said, it works flawlessly the first time

#

Just when it's brought back, the options to delete transcript and all that is missing

#

and when closing, no overwrites are removed from the ticket owner

#

@fleet orbit

Okay, sorry for the hassle. Turns out the bot just hit a ratelimit(?) or had bad latency and didn't send the follow-up embed. I just checked the channel and the embed was sent almost 10 minutes later

fleet orbit
topaz shore
#

But that shouldn't affect overwrite or message limits

fleet orbit
#

Interesting.. I'll need to see why it didn't handle it.

fleet orbit
topaz shore
#

Ah, I see

fleet orbit
#

I'll look into this and see if I can find out why my checks didn't catch that rate limit.

topaz shore
#

Sounds good. Thanks for your time and I'll leave it with the smart people now lmao

fleet orbit
#

Otherwise everything worked fine?

topaz shore
#

Not sure whether I should close this ticket or anything

#

Yes

fleet orbit
topaz shore
#

Okay

#

I think Discord itself may be having troubles not your end tho

#

Because now simply creating a ticket isn't working lmao

#

Just stuck on the intial response of "creating.."

topaz shore
#

@fleet orbit Do you have updates on this btw? We still encounter issues where the bot has a delay when sending the follow-up embed after closing the ticket.

winter owl
topaz shore
#

It's the same issue at the end of our last conversation @winter owl

#

Related to things not being sent correctly