#already ack

1 messages · Page 1 of 1 (latest)

waxen cypress
#

you have already responded to this interaction

robust fjord
#

i dont know where though

#

its not in my code

waxen cypress
#

if you need to edit #editReply, if you want to send additional messages, follow-ups are the way to go

robust fjord
#

when i defer, it says already acknowledged though

#

so i dont think thats it

waxen cypress
#

well, you can think pretty much anything

#

but that's what that error means

#

means you are responding to an interaction that you already responded to

#

so either already deferred it or acknowledged it with another response

robust fjord
waxen cypress
#

from that code i don't think so, the two edits are in diff. branches

#

maybe your command handler or some other code already responds before you defer in 55?

robust fjord
#

okay ill take a look

waxen cypress
#

seems to be a type 4 response

CHANNEL_MESSAGE_WITH_SOURCE

so should be a #reply call
defer would be 5
defer reply would be 6

robust fjord
#

I mean I was getting the error for defer as well

#

I just sent the error code for when I tried without deferring

waxen cypress
#

2022-02-14T20:17:06.664279+00:00 app[worker.1]: requestData: { json: { type: 4, data: [Object] }, files: [] }
this points to a reply
not editReply, not defer

so that'd suggest the cause is Interaction#reply after you already replied/deferred/whatever to the same interaction

robust fjord
#

oml its the handler

waxen cypress
#

eyup, that'd cause that