#beastboy_best-practices
harsh eagleBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1285602828714381444
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
warped moon
No, I don't believe there is any explicit indicator for that. Why does it matter? What are you trying to do, exactly?
nimble ice
I want to resend a webhook for a customer so their paid event gets re-processed by our system, but we send order confirmations to the customer along with the paid event. Because we don't want to resend it to our customer, I'd like to add in some 'flags' in the code to not send it.
something like, if this is not a resend, send order confirmation email
warped moon
Ah, in that case I would say thats something to track in your own system
either by the event id, or for the order, not to send the confirmation email again
nimble ice
😦
warped moon
instead of relying only on the stripe event data
nimble ice
I see
vague needle
Hi there 👋 jumping in as my teammate needs to step away soon. You can also try to use the --param option when resending the Event from the Stripe CLI to include a key/value pair on your request. It's not something I've tried before so I'm not exactly sure how it plays out, so I'd recommend testing in testmode first:
https://docs.stripe.com/cli/events/resend#events_resend-param
nimble ice
yeah so ive been trying that, but when I do I keep getting 'unknown flag: --param'
does this param still work?
vague needle
I would need some time to test, but without more context I'd be suspicious of the CLI version that you're using. Maybe it's before support for param was added?
nimble ice
Just updated it and I get the same error back
vague needle
Gotcha, I would suggest trying to use the -d or --data option then.
Something like:
stripe events resend evt_1Q02PwABPeS8n8ReYYlGzayP -d resend=true
nimble ice
yeah tried tha too, but got:
{
"error": {
"code": "parameter_unknown",
"doc_url": "https://stripe.com/docs/error-codes/parameter-unknown",
"message": "Received unknown parameter: resend",
"param": "resend",
"type": "invalid_request_error"
}
}
vague needle
Can you paste the whole command you're using?
nimble ice
stripe events resend evt_1PqNvPDyFtOu3ZuTBw6gVCpk -d resend=true
vague needle
Hm, I'm seeing the same, trying to update to see if that resolves it.
nimble ice
its already updated
vague needle
Yeah, I'm seeing the same, I'll work on reporting that to our teams, but it seems what you're wanting to do isn't possible at the moment then.