Guides
A useful place to start, with a route to the related result.
Guides 49–72 of 348
Troubleshooting guide
Keep application access correct when a Stripe subscription changes
Map purchase, renewal, failed payment and cancellation to an explicit access policy instead of trusting a success page.
Troubleshooting guide
WordPress critical error after an update: collect evidence without exposing debug output
Use existing logs and an isolated test copy to identify the first fatal error instead of disabling every plugin on the live site.
Troubleshooting guide
Diagnose WooCommerce checkout conflicts after an update
Isolate the failing theme or plugin on staging and prove the same product, shipping and test-payment journey works again.
Troubleshooting guide
An Airtable automation failed or did not run: read the history, then check five causes
Find the failing step in the run history, understand why records already matching never trigger, and check inputs, scripts, limits and who gets told.
Troubleshooting guide
Splitting a repetitive Airtable table into linked tables: how the matching works and where it goes wrong
Why exact text matching, commas and formula primary fields matter, and the order that keeps counts reconcilable when one table becomes two.
Troubleshooting guide
A scheduled job that asks for records since its last run: why it loses some and repeats others
Four small pieces make polling reliable: a checkpoint, an overlap, a key for every record and complete paging. See why each exists.
Troubleshooting guide
Who is told when an automation fails? What each tool really does, and how to test it
Zapier, Make, n8n and Airtable each alert in different ways, with delays, gaps and side effects. Find out where yours goes, then test it by breaking a copy.
Troubleshooting guide
Verify a webhook signature on the exact bytes you received, not the data you parsed
Why a correct secret can still fail, how to compare signatures safely, which identifier to trust against replays, and how to test a receiver with known inputs.
Troubleshooting guide
The sender says webhook delivery failed: timeouts, retries, deleted subscriptions and missed events
Answer quickly, expect repeats, and know how to find and replay events that arrived while your endpoint was down.
Troubleshooting guide
Duplicate HubSpot contacts or companies after a web form: which route created them
HubSpot matches contacts by email and companies by domain, but the route a lead takes decides what happens. Learn the four routes and the risks of merging.
Troubleshooting guide
New HubSpot leads with no owner: how rotation, away users and fallbacks really behave
Write the routing rules first, then learn what the rotate action counts for contact records, how HubSpot's Leads tool differs, and where a lead ends up when nobody is available.
Troubleshooting guide
A HubSpot field keeps changing back from Salesforce: sync rules, baselines and picklist errors
Read the sync rule on the field, understand the first-sync baseline, then check types, picklists and where HubSpot lists sync errors.
Troubleshooting guide
A Zap created the record twice: find which of five causes it was
Count the runs, then check for a second Zap on the same trigger, a self-trigger, a replay and a plain create step before you change anything.
Troubleshooting guide
A Zap stopped or shows Errored or Halted: what each status means and what to replay
Read the run status first, understand why a Zap turns itself off, and know what a replay repeats and why error emails can arrive hours late.
Troubleshooting guide
A Make scenario stopped on one record: error handlers and incomplete executions explained
What Make does by default when a module fails, what the five error handlers do, why a route that only sends a message skips the error, and why a stored incomplete execution can hold back the next run.
Troubleshooting guide
A scheduled report arrived at the wrong time or covered the wrong days
Find out which clock your automation tool uses, fix the reporting period in one place, and test across a clock change instead of assuming.
Troubleshooting guide
An n8n webhook works while you watch but not afterwards: test and production URLs
The Webhook node has two addresses with different rules. See which one your sender uses, how to read production runs, and how to be told when one fails.
Troubleshooting guide
CI reinstalls dependencies on every run: find out why the cache never hits
How a CI dependency cache is looked up, five reasons it never serves a later run, a safe two-run comparison, and how the paid fix is accepted.
Troubleshooting guide
A CI job runs for hours and is then cancelled: find what is waiting
Why a hung job shows no error, the usual waiting processes, a safe way to locate the one in your job, and what a lasting fix looks like.
Troubleshooting guide
CI job killed or out of disk space: measure the limit before buying a bigger runner
What a killed process and a full disk look like, what a standard hosted runner actually has, how to measure peaks on a branch and which fixes reduce demand.
Troubleshooting guide
A flaky test: how many clean repeat runs show that it is fixed?
Why a green re-run proves nothing, how a failure rate turns into the number of clean runs you need, where flakiness hides, and how to investigate on a branch.
Troubleshooting guide
A CI secret exists but the job gets an empty value: check where the run may see it
Four reasons a secret you created is not visible to a job, how an unset secret fails later and elsewhere, a safe presence check, and what is yours to change.
Troubleshooting guide
GitLab job never starts: tell a missing pipeline from a job no runner will take
Two different faults with the same symptom: a merge request with no pipeline, and a job stuck pending. How GitLab decides each, a read-only check and what you can change yourself.
Troubleshooting guide
A Docker image builds on your laptop but not in CI: compare what the clean checkout lacks
What changes between a laptop build and a clean CI build: the build context, ignore rules, build arguments, secrets and cached layers, with a read-only comparison.
A need we have not covered yet?
Tell us what you need accomplished. We confirm whether we can offer a useful scope before accepting work.
Describe a custom outcome