#monove

1 messages · Page 1 of 1 (latest)

jovial gardenBOT
pallid charm
#

hello! do you have the request id where you attempted this?

copper hawk
#

no. we're using the dashboard

pallid charm
#

000000000 - have you tried 9 0s?

copper hawk
#

worked. sorry.

#

on another topic.
can you look up why req_nmSDczNpZXaq6f failed

pallid charm
#

where's the request or which account id did you create the deploy group on?

copper hawk
#

req_kgwzPcQvIcNksu

#

we also tried with a different deploy group (created req_7YpDG9we93PvIp) and got the same error: req_5JMndBLokArkNG

#

our platform account is a controller

#

my suspicion is that either our platform account or the connect account haven't been gated in

pallid charm
#

do you have a different account where these requests are working?

copper hawk
#

all the API calls were made from our platform account with the Stripe-Account header, so no. theoretically i could get their secret key and do it that way but that is not smart and i cant imagine you'd want that

#

all the calls work besides that call

jovial gardenBOT
copper hawk
#

take a look and you'll see i just created a deploy group (req_7YpDG9we93PvIp), device asset version (req_AbHG3SotSfhBAX) and a deploy plan (req_QqWKXLJZagDZEP) successfully

pallid charm
#

@copper hawk i think it's best if you reach out to your Stripe Contact (i'm assuming you have one), or write in at https://support.stripe.com/contact/email with those request ids and describe your problem. We aren't so familiar with deploy groups for terminal here on your channel so it'll take us a while to invesitgate. If your Stripe contact has spoken with you about using deploy groups for Terminal and there's certain features that need to be enabled for your account in order to get that working, they'll be able to redirect your problem to the right team to get that fixed quickly

copper hawk
#

I did write in, multiple times and have not received a response. I will try again as you advised and I will add all the request id's as you advise.

pallid charm
#

hmmm, let me try and track down your support ticket too

#

do you know which account id you wrote in from for this issue?

#

is it the ticket where you wrote in about req_9vxlCCS0gW3iqD?

copper hawk
#

no, thats a different issue which is also dragging

#

we were responding to an earlier email regarding the invite. i had referenced req_KnJuSUCzx8zR17

#

can you make this thread private?

pallid charm
#

that can't be done unfortunately - but i think i can delete the thread if you're concerned. The request ids aren't information that can be accessed outside of your account so it's not sensitive information

copper hawk
#

i can provide more info if you need more

pallid charm
#

trying to track down req_KnJuSUCzx8zR17 in the content isn't working for me. I think i'm going to need the account id you wrote in from to track down that support email, or you can write a new support ticket from
acct_18esDcFVvfxwXzwr - and once that's sent let me know so i can track it down and get that flagged/routed to the right team

copper hawk
#

acct_18esDcFVvfxwXzwr

#

i'll write in a new support ticket

#

if i write it in now, would you be able to prioritize it?

#

also, which email do i write into

pallid charm
#

i'll flag it to the relevant team, but they're based in the US so it'll take them a while to get back to you

copper hawk
#

a while like a week?

pallid charm
#

i would say they should acknowledge your email within 24 hours, how long it takes to resolve the issue i can't say though

copper hawk
#

ok

#

i should just select "Terminal"? or is there a more specific option i should select?

pallid charm
#

just terminal is fine

copper hawk
#

thanaks

pallid charm
#

let us know once you've sent it. I just checked again and I don't see any new tickets under acct_18esDcFVvfxwXzwr yet

copper hawk
#

almost done

#

done