Stripe paid, WooCommerce pending: reconcile the order
Match the payment, its event and the order status.
KAN KAI WORKS · Help
Search for your product, an error message or the problem you can see. Each guide explains how to narrow it down and what information helps with further investigation.
For example Stripe, Request_Helper, R041, n8n or missing email.
Try a product name or a shorter error code. You can also show all guides or describe your issue.
Match the payment, its event and the order status.
Distinguish actual captures from authorisations and duplicate displays.
Check the data source, transfer and destination separately.
Check a paid order’s download permission, remaining allowance and file delivery before regenerating access.
Separate an empty cart, browser history behaviour and genuine session failure with a reproducible navigation test.
Use the failed file response to distinguish access blocking, missing assets and stale references behind a ChunkLoadError.
Check the gateway, display location and eligible wallet environment before rebuilding domain registration or payment settings.
Reconcile payments and orders first, then trace the missing reference in the specific checkout attempt.
Inspect the exact Store API error and fresh-versus-aged page output without disabling security validation.
Compare the saved checkout type with the PayPal scripts actually loaded when the payment area is unusable.
Check customer assignment, order state and the payment link before changing permissions or the PayPal connection.
Separate a display discrepancy from actual refunds and reconcile each attempt using its PayPal reference.
Compare cart, creation, update and capture amounts, and evaluate the correction reported for the affected plugin version.
Trace connection, job execution and one specific order to the intended Mailchimp audience.
Check the exact error and the related plugin versions.
Trace one clearly marked test message.
Investigate a missing status element and JavaScript failure when the form never starts a submission request.
Correlate the failed save request with PHP and server logs before treating memory as the cause.
Find the first editor failure and compare PHP environments before assuming a general version incompatibility.
Measure the complete save request and identify the rejecting server layer before changing upload or security limits.
Identify the failing child sitemap, request duration and server error, and separate processing failure from a blank display.
Compare every child sitemap as a URL set, separating genuine omissions from variations, noindex and canonical addresses.
Check the affected older version, error path and PHP intl availability, including the correction reported in the original case.
Compare the client ID and callback actually sent with the same Google OAuth client’s registered configuration.
Trace the path from QUIC.cloud to the local image and find the missing step between optimisation, retrieval and storage.
Distinguish a missing form field from an expired token and compare roles with the ESI-generated output.
Test a first-time guest separately from a repeat visitor and isolate the JavaScript or CSS optimisation involved.
Compare large inline CSS, the parser error and generated resources; an optimisation notice alone does not prove success.
Check the original file, transfer integrity and import route without overwriting the last usable backup.
Distinguish a running import from a failed background request or a PHP error in a restored theme.
Separate displayed PHP values from the effective browser, web-server and security-layer limits.
Check the media address in the export, source availability and destination file processing as separate stages.
Match the complete rejection to the actual sending path and check SPF, DKIM and DMARC according to the evidence.
Compare server, port, TLS mode and authentication when Thunderbird rejects the selected method.
Check OAuth handoff, package type and profile separately when Google authorises access but Thunderbird cannot connect.
Identify whether authentication, one message or local storage is holding up mail retrieval.
Check server contents, folder visibility and the documented IMAP compression regression before recreating folders.
Back up large Thunderbird profiles completely and test restoration before retiring the old computer.
Compare the public response, connector and origin separately.
Separate request arrival, execution storage and the target system.
Assess needsDbUpgrade and an already existing table safely.
Identify the OAuth client and preserve existing backups before authorising the Drive connection again.
Check the bootstrap file, actual website path and PHP configuration in the correct order.
Choose an authorised owner-recovery route and fully re-establish two-factor protection afterward.
An n8n run failed after the target already processed its request? Reconcile business references and retry behaviour before repeating the action.
n8n cannot reach an HTTPS API that opens in your browser? Separate connection establishment, source network and HTTP response.
Postgres connection fails with a certificate-chain error? Check the endpoint, trust chain and the differences between Cloud and self-hosting.
Item links fail after Get row(s)? Check match counts, empty results and business IDs before data is assigned to the wrong record.
429 or concurrency errors after n8n branches converge? Inspect node invocations, item counts and the intended aggregation separately.
Publication reports an existing name after deployment? Compare the running n8n version with database migration history before duplicating workflows.
Scheduled processing goes quiet? Check publication, timezone and expected business output, then monitor missed successful runs.
Blank n8n editor or repeated disconnects? Separate browser, connection and backend health without replaying active operations.
Instagram test events work but real messages are missing? Trace event delivery, the public route and the n8n production endpoint.
Executions remain queued or the instance restarts? Inspect backlog, active runs and workload before replaying incoming events.
A corrupt SQLite database stops n8n? Preserve the original, companion files and key, then assess recovery on an isolated copy.
A hostname fails to resolve from n8n? Inspect container DNS, service names and destination ports in the relevant network.
Saving fails with Sabre DAV Locked? Identify the lock mechanism and distinguish it from filesystem permissions before removing anything.
An update stops at its write-permission check? Identify the exact path, effective PHP user and mount permissions before changing ownership.
Upload limits or PHP values remain unchanged? Compare web SAPI, CLI and the configuration actually loaded before reinstalling PHP.
Office connection appears healthy but documents will not load? Check browser access and both server-to-server connection directions.
Team files remain on storage but folders disappear from Nextcloud? Check app state, folder configuration and group access before recreating them.
Unknown files detected within the installation folder? Identify the reported files and preserve evidence before cleaning the installation.
Files disappear after a mount or sharing change? Pause synchronisation, preserve local copies and establish server and storage state.
Reading works but saving returns Permission denied? Distinguish a local bind mount from SMB access and identify the effective writing identity.
AIO reports a domain or reverse-proxy problem? Check DNS, APACHE_PORT and the upstream actually reachable from the proxy.
Opening a webhook URL returns Unauthorized? Check its API-key header, IP rules and actual hook identity without removing protection.
A Google connection exists but Sheets or Drive return 403? Separate OAuth completion, connection identity and access to the actual file.
An incomplete Make execution fails at an aggregator? Inspect saved run state, Source Module and data completeness before restarting.
Several spreadsheet rows but one result? Compare spreadsheet ID, sheet, range and the actual module output before downstream filters.
curl works but Make returns a parameter-validation error? Compare the transmitted JSON body, headers and resolved values.
The source contains several items but Iterator receives nothing? Check the field path, array type and module reference in the same execution.
A later Stock Reconciliation blocks an earlier batch entry? Inspect document chronology, affected batch and version before changing records.
Installation requires incompatible Tenacity 8.2 and 9.1 ranges? Compare exact app revisions and dependencies instead of forcing alternating versions.
CRM assets fail with MISSING_EXPORT after a Frappe update? Compare the component interface and matching CRM version before applying local patches.
Check the DuckDNS response, domain ownership and published TXT record when SWAG cannot renew its wildcard certificate.
Trace A, AAAA and CNAME answers to the authoritative servers when Certbot fails with DNS SERVFAIL.
Compare IPv4 and IPv6 on the same challenge path when the website works but certificate renewal fails.
Check the actual Certbot executable, authentication method and scheduler separately before a certificate expires unnoticed.
Identify the unsupported authenticator combination and plan a renewable DNS challenge for your wildcard certificate.
Compare nginx’s certificate path with the actual file, startup directory and permissions before issuing replacement certificates.
Compare the same challenge path from independent networks and match both successful and missing requests to your logs.
Separate the DSM message from a confirmed ACME rate limit and check domain validation and certificate assignment.
Separate resolver reachability, DNS policy and UDP/TCP behaviour when WARP can no longer resolve internal names.
Distinguish UDP reachability from a successful QUIC handshake and run a limited HTTP/2 comparison where appropriate.
Check name resolution inside the connector environment when a .local service works on other devices.
Trace Location headers and the origin scheme when an application enters a redirect loop through the tunnel.
Compare saved remote configuration, expected units and elapsed time when an origin request times out immediately.
Trace the WebSocket handshake to the origin when live updates fail but ordinary HTTP requests still work.
Locate the affected allowance or charge in the XML.
Distinguish generation failure from a display issue.
Separate visible-signature font errors from token access and cryptographic signature validation.
Compare the crop preview with saved output on clearly identifiable pages when the selected area shifts.
Check the saved PDF for old text and distinguish editing, covering and permanent removal.
Measure opening, navigation and server processing separately when technical drawings become difficult to use in the viewer.
Compare ID-token claims, UserInfo and supported user mapping when Entra sign-in fails in Stirling PDF.
Separate a broken validation report from an invalid invoice and compare identical contents under a neutral filename.
Read PDF/A, invoice XML and overall results separately when wasCompletelyValid returns true despite a PDF failure.
Compare complete rule bundles, scenarios and versions when the same XRechnung passes one check and fails another.
Locate the exact numeric field and separate XML formatting errors from overly strict importer handling.
Reconcile line totals, document allowances, charges and the payable amount separately when import reports an arithmetic difference.
Editorial policy, sources and scope →
Describe the affected system, the visible problem and when it started. That gives us a starting point for the next check.
Describe a different issue →