ResponseAysnc completes without sending a message (Yes, my clock is synced.)

[cunning scaffold]

I have a stripped down command for the purposes of troubleshooting. This command simply takes one argument and responds with a stock message. It looks like this:

[SlashCommand("test_command", "test")]
public async Task TestCommand(string testArgument) {
    await RespondAsync("Nice try!").ContinueWith(t => Console.WriteLine("Test"));
}

When I run the command from a server and channel where it has Send Messages permissions, the string "Test" appears in the console, but the message "Nice try!" fails to arrive in the server, as shown in the attached image. The application has bot and slash command permissions. I have no idea what I'm missing, but at times like these the answer is often obvious I merely overlooked. Regardless, any help would be appreciated. Thanks.

Also for reference, the command is in a module with the following:

[CommandContextType(InteractionContextType.Guild, InteractionContextType.PrivateChannel, InteractionContextType.BotDm)]
[IntegrationType(ApplicationIntegrationType.UserInstall, ApplicationIntegrationType.GuildInstall)]

although I don't think I would have gotten this far if I had failed at this stage.

[glass ridge]

Sync your system clock

[cunning scaffold]

My system clock is synced. I have restarted my computer, checked again that my system clock is synced, and re-tested my code. It still fails in the same way

[cunning scaffold]

ResponseAysnc completes without sending a message (Yes, my clock is synced.)

[cunning scaffold]

For additional context, there is a distinct message for MyApplication did not respond in time. That is not what's happening here. I'm simply getting the above message The application did not respond.

[glass ridge]

#discussion message

[nocturne wave]

exsersewo

Message:

discord.net default behaviour is to set the interaction receive from snowflake, if you are more than 3 seconds out of sync, all interactions fail to respond until it gets resynced or this gets set #discussion message

Quoted By:

@glass ridge from #discussion in Discord.Net

Sep 18, 2024, 8:29 PM

[cunning scaffold]

My system is offset by less than a milisecond from NTP time.

I have also tried setting the APIOnRestInteractionCreation field equal to false, as was suggested in the same discussion. That did not seem to help.

I think it's worth mentioning that the console log "Test" appears within a second of issuing the command. Given that I've successfully responded to a ping, though, I'm once again at a loss.