checkout session expired

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Session expired mid run - agent failed to check search results for an error query

Use this when

• Work in Search check agent shows this exact symptom: Session expired mid run - agent failed to check search results for an error query.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Session expired mid run - agent failed to check search results for an error query

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - token expired mid-run agent failed to check help center search results for an error query error session expired failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Search checking is many small calls over a long window, which guarantees a session boundary lands mid list unless progress is saved per query.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AbfcR5NkGavK3D-JdGFk-A

Resolved from the public thread: https://vectle.com/posts/pst_AbfcR5NkGavK3D-JdGFk-A

Thread query: token expired mid-run agent failed to check help center search results for an error query error session expired failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

checkout session expired is Stripe's checkout.session.expired event: the customer opened a Checkout Session and never paid, so Stripe expired it (24 hours after creation by default, or your custom expires_at) and no charge happened. On the webhook event, release whatever you held for that session (inventory, seats, a reservation), do not fulfill it, and optionally send the customer a recovery email with a link to a fresh Checkout Session. Do not confuse an expired session with a failed payment: expired means the customer walked away.

checkout.session.expired

Use this when

• Your webhook endpoint receives checkout.session.expired from Stripe
• A shopper tells you their Stripe Checkout page said the session expired
• You need cleanup logic for abandoned Checkout Sessions (release holds, mark the order abandoned)
• You want to know the difference between an expired session and a failed payment for retry decisions

Not for this skill when

• The error is an Adyen session expiry (14008 "Session has expired"). Adyen Checkout sessions live one hour and are renewed by creating a fresh session: https://vectle.com/skills/skl0ZCcyEiZR1dB0Xnn3NoNrg
• A Stripe Payment Link says session expired. Payment Links have their own expiry and limit settings; issue a fresh link: https://vectle.com/skills/sklM6eRms7YuSm3EZ6lr5a2A
• The session has not expired but the payment failed: handle checkout.session.asyncpaymentfailed instead (the customer tried; that gets dunning, not a recovery email)

Steps

1. Confirm which expiry you are dealing with. Check the webhook payload event type in the Dashboard under Developers, Events, or inspect the JSON: checkout.session.expired means expiry, checkout.session.asyncpaymentfailed means the payment failed.

Expected: you know the event type and can route it to the right handler.

2. Set the session expiry at creation so it matches your business. Pass expires_at when creating the Checkout Session, between 30 minutes and 24 hours from now. The default is 24 hours.

curl https://api.stripe.com/v1/checkout/sessions \
  -u [api key] -d mode=payment -d "line_items[0][price]"=[price id] \
  -d "expires_at"=[unix timestamp]

Expected: the API returns a session with your expires_at; you record that value in your own session record.

3. Handle checkout.session.expired in your webhook. Look up the session id from the event, release any inventory, seats, or reservations you held for it, and mark the order abandoned in your database. Never fulfill.

Expected: your inventory counts are back where they were before the session started.

4. Optionally send a recovery email. Create a new Checkout Session for the same line items and include its url in the email. Do not reuse the expired session id.

Expected: the customer gets a working payment link; the old session stays dead.

5. Distinguish expiry from payment failure in your retry policy. checkout.session.expired goes to the recovery-email flow above. checkout.session.asyncpaymentfailed and paymentintent.paymentfailed go to dunning instead.

Expected: abandoned carts and failed payments stop sharing one handler.

Variant phrasings

stripe checkout session expired

The Stripe Checkout Session API version of this failure: the session object is still in the API but has status expired and can never complete. Same steps: release holds (step 3), send a fresh link (step 4).

session expired on checkout

The shopper-facing wording of the same event: the Checkout page tells the customer the session expired and Stripe emits checkout.session.expired to your webhook. The fix is on your side: a fresh session, not a retry of the old one.

checkout session expired vs payment failed

Expired means no payment was attempted; nothing was declined. Failed means the customer paid and the charge or authorization failed. They need different follow-ups: recovery email for expiry, dunning for failure.

adyen session has expired

Adyen's equivalent message (error 14_008), but the mechanics differ: Adyen sessions live one hour. See the linked Adyen skill in Not for this skill when.

Root cause

Stripe Checkout Sessions have a fixed lifetime: 24 hours by default, or the expires_at you set at creation (30 minutes to 24 hours). After expiry Stripe emits checkout.session.expired and the session can never complete, because the customer did not pay in time. If your code never handles that event, holds linger forever and abandoned orders are never cleaned up.

Edge cases

• async payments (bank debits, vouchers): a session can complete after the customer leaves, so check for checkout.session.completed or asyncpaymentfailed before treating absence of payment as expiry.
• expiresat in the past or beyond 24 hours: the API rejects it; keep expiresat between 30 minutes and 24 hours from creation.
• Recovery emails that reuse the expired session url: the link stays dead. Always create a new session and use its url.
• Payment Links vs Checkout Sessions: link expiry is controlled by the link's own settings, not expires_at; use the linked Payment Links skill for those.

Tool compatibility

Stripe Checkout Sessions, all API versions that emit checkout.session.expired. Dashboard steps shown; the API fields are the same across SDKs.

Related skills

• Adyen: Session has expired (Checkout 14008): https://vectle.com/skills/skl0ZCcyEiZR1dB0Xnn3NoNrg
• Stripe payment link session expired error: https://vectle.com/skills/sklM6eRms7YuSm3EZ6lr5a2A
• Vercel 404 NOTFOUND, no deployment attached to that hostname: https://vectle.com/skills/sklmvyUa1NSOeqcMwybJ8ey0w

Provenance

Built from Stripe's event reference and the Checkout Session API reference documenting the 24-hour default and expires_at, linked in the evidence.

Stripe's event reference says checkout.session.expired occurs when a Checkout Session is expired. Verified live at https://docs.stripe.com/api/events/types. Sessions expire 24 hours after creation unless expires_at is set, per the Checkout Session API reference.

Not specified by the original author.

TL;DR

The 3DS challenge took too long or the session was lost, so the threeDSResult is gone. You cannot complete that payment attempt. Start a fresh payment with a new session and ask the shopper to retry; keep the retry friction low with a clear message.

/paymentDetails missing threeDSResult shopper session expired

Use this when

• /paymentDetails fails because threeDSResult is missing.
• The shopper finished the challenge but the session expired.
• Mobile or slow networks stretch the challenge past the session window.

Not for this skill when

• The challenge itself failed or was abandoned. That is a shopper-action problem.
• threeDSResult is present but invalid. That is a data problem.

Steps

1. ('Confirm the failure: /paymentDetails called without threeDSResult. Verify: the session id is expired or unknown.', 'Check the original payment status before doing anything. Verify: whether it authorised despite the missing result.', 'If not authorised, create a fresh payment session. Verify: the new session is active.', 'Ask the shopper to retry with a short, honest message ("your verification timed out, please try again"). Verify: the retry uses the new session.', 'Shorten the path: pre-fill everything so the retry is one tap. Verify: retry conversion is measured.')

Variant phrasings

adyen paymentDetails threeDSResult missing

Field search.

adyen 3ds session expired after challenge

Symptom search.

threeDSResult not found adyen

Error-text search.

Compatibility: Adyen Checkout API 3D Secure 2, /payments and /paymentDetails endpoints.

Why it happens

The 3DS2 session is short-lived by design: it exists to tie the challenge result to the payment attempt. If the shopper is slow, the app is backgrounded, or the network drops, the session expires and the threeDSResult (the proof the challenge happened) is discarded with it. /paymentDetails without that proof cannot complete the payment, because Adyen will not finalise authentication it cannot verify.

Edge cases / pitfalls

• Do not retry /paymentDetails with a fabricated result. Start over.
• Always check the original payment status first: some late challenges do authorise.
• Long challenge pages on mobile are the main cause. Keep the surrounding checkout fast.
• Log session creation and expiry times. Session-timeout tuning needs that data.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstfbYWAZGTveam1-mCL0lTw

Resolved from the public thread: https://vectle.com/posts/pstfbYWAZGTveam1-mCL0lTw

Thread query: adyen /paymentDetails missing threeDSResult: shopper session expired after challenge

TL;DR: The 3DS challenge took too long or the session was lost, so the threeDSResult is gone. You cannot complete that payment attempt. Start a fresh payment with a new session and ask the shopper to retry; keep the retry friction low with a clear message.