#tymm
1 messages · Page 1 of 1 (latest)
Hi there, I don't think search API support resources created with test clocks yet
i have been using it and it's been working fine tho only recently it is not working and i did not change anything on my end atleast not the query method
were the previous query for objects created in test clocks as well?
yeah always has been
Can you share with me the request ID?
of?
the search query you did previously that returns non-empty result.
i do not know which of the older records have it since the dashboard doesnt show the response but this one should have it req_ZWRioIehLu7Ixo
Thanks for waiting. I was wrong. The search API returns objects created in test clocks as well.
Under normal operating conditions, data is searchable in less than a minute. Occasionally, propagation of new or updated data can be up to an hour (https://stripe.com/docs/api/subscriptions/search?lang=cli#subscriptions_search)
Can you try it again later?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
anyway another problem, i have created a customer, and i wanted to attach a paymentmethod to it. i have this snippet here to show that the customer was created (at least stripe is telling me so), but when tried to create a setup session it gives me error no such customer. i cant find the customer in my dashboard either.
{
"address": null,
"balance": 0,
"cash_balance": null,
"created": 1677723163,
"currency": "myr",
"default_source": null,
"deleted": null,
"delinquent": false,
"description": null,
"discount": null,
"email": "peishan.chang@securemetric.com",
"id": "cus_NRvUr535S0LuJv",
"invoice_credit_balance": null,
"invoice_prefix": "F7D5A6B4",
"invoice_settings": {
"custom_fields": null,
"default_payment_method": null,
"footer": null,
"rendering_options": null
},
"livemode": false,
"metadata": {
"account_id": "10076"
},
"name": "acc_10076",
"next_invoice_sequence": 3,
"object": "customer",
"phone": null,
"preferred_locales": [],
"shipping": null,
"sources": null,
"subscriptions": null,
"tax": null,
"tax_exempt": "none",
"tax_ids": null,
"test_clock": "clock_1Mh1dPLK0bfo5HSbqK8wyDlU"
}
No such customer: 'cus_NRvUr535S0LuJv'; code: resource_missing; request-id: req_6b3VgmlDTpSzKh
this customer is created in a test clock, and Checkout Sessions API doesn't support test clock
in this request i create the customer without testclock. but for some reason it shows testclock in the response, perhaps it was due to a customer with same name and email was created prior to this? i deleted that customer before creating this one just to test if things work without testclock.
also, customer with testclock does with with sessions api:
req_F0xHIELT4bO5TO
req_cygRqYvqECqCd8
https://dashboard.stripe.com/test/logs/req_aVmlWVuRH8vqZ1 there's a test_clock in the customer creation request.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
something wrong with the api server today? seems like its not responsive
i cannot see this in my log tho
about the checkout session creation error, that's because customer cus_NRvUr535S0LuJv is already deleted. (https://dashboard.stripe.com/test/customers/cus_NRvUr535S0LuJv) when the checkout session creation request is made
I made a mistake previously, the checkout session API do support customer created with a test clock.