Find the outcome you need.
Start with a symptom, a platform or the thing you want working.
With JavaScript, search filters the whole collection in your browser. Without it, use the linked pages and section navigation below; query filters need JavaScript.
Showing entries 761–787 of 787 in this first collection.
Collection
Your WordPress site changed after an update: where to look first
An ordered path from fatal errors to single features, layouts, PHP versions, lost theme edits and changed addresses, ending with how to stop it recurring.
Inspectable example
Synthetic CI buying comparison: a fee difference is not a scope or savings verdict
Compare invented DIY and tool effort with the existing £149 one-job and £295 monthly offers, keeping hypothetical workload, customer work and untested prices visible.
Inspectable example
Synthetic CI monthly ledger: six red attempts are not six accepted fixes
A made-up failure ledger separates repeat attempts, one repaired cause, a flaky test, an account action and an unmerged proposal before discussing a monthly allowance.
Troubleshooting guide
Who owns a flaky CI test? Separate investigation, quarantine approval and the product fix
An intermittent pass does not establish repair. Assign the evidence, temporary risk decision and actual test or application correction before buying a repeatable-job fix.
Troubleshooting guide
What does a red CI build cost? Separate runner usage, active work and blocked time
Use job-level usage and actual investigation effort without multiplying a red badge by every engineer's salary or treating included minutes as cash savings.
Troubleshooting guide
Your CI maintainer is leaving: transfer responsibility, not just workflow notifications
Before a supplier ends or an engineer leaves, assign the open failures, alerts, merge authority and credential revocation without assuming a green last run proves continuity.
Inspectable example
Synthetic invoice reconciliation: identical net lines, two different tax totals
Three invented small-value lines show how line-level and invoice-level tax rounding can disagree even when net values and line counts match.
Inspectable example
Synthetic invoice retry matrix: source operation, attempt and target draft are different IDs
Concrete made-up references specify when a retry retains one target draft and when changed contents, a second organisation or multiple matches need a separate decision.
Collection
Invoice integration review: verify shape, representation, tax basis and repeat safety
An ordered review worksheet helps a finance owner stop at the first broken contract before requesting a bounded existing mapping repair.
Troubleshooting guide
Invoice values look right in Sheets but arrive as currency text or a date number
Separate a spreadsheet's displayed currency and date from the values a connector reads, then agree the destination types before repairing a mapping.
Troubleshooting guide
An invoice integration adds tax twice: agree whether each amount is net or gross
Name the tax basis of each mapped line and the approved tax treatment before mistaking a populated amount field for a correct invoice.
Troubleshooting guide
Invoice creation timed out: reconcile the unknown result before retrying
Distinguish a confirmed rejected creation from a lost response after a possible write, and define zero, one and conflicting-match dispositions before a replay.
Inspectable example
Synthetic supplier-key matrix: zeros, long codes, reused SKUs and an unmapped item
Four invented product mappings expose numeric coercion and cross-supplier collisions; an unknown key stays unassigned instead of becoming a guessed product.
Inspectable example
Synthetic supplier-update contract: blank price, absent field and missing product
A worked decision matrix separates a field omitted from a partial update from a product absent from a complete snapshot, with explicit hold and no-change results.
Inspectable example
Worked pack-price example: why 36 items cost 59.97, not the rounded display total
An invented USD 19.99 pack of 12 distinguishes the purchase basis from a rounded per-item comparison and shows exactly where a misleading total arises.
Inspectable example
Synthetic feed-disposition sequence: newer, late, repeated and conflicting updates
Starting at supplier version 41, a six-step expected-state sequence shows when a feed changes the accepted version and when the previous state must remain intact.
Troubleshooting guide
Supplier SKUs lose leading zeros: preserve the identifier before importing
Keep supplier identifiers textual and compare exact keys before a stock or price feed creates a second product or updates the wrong one.
Troubleshooting guide
Two suppliers use the same SKU: match the supplier and code together
Prevent one supplier's stock or price from landing on another supplier's item, and keep unapproved cross-supplier mappings out of an automatic update.
Troubleshooting guide
A supplier feed repeats one key with different prices: reject the conflict before updating
Distinguish an identical duplicate from conflicting rows and choose a documented disposition instead of allowing file order to decide a business value.
Troubleshooting guide
Blank supplier price clears a good value: distinguish unchanged, empty and explicit removal
Give missing fields and blank cells different update meanings before a partial supplier feed erases a price or silently substitutes zero.
Troubleshooting guide
An item disappears from a supplier feed: is it a full snapshot or just a delta?
Do not turn an omitted SKU into zero stock or discontinued status until the source defines completeness, coverage and deletion semantics.
Troubleshooting guide
Supplier quotes per pack, your app compares per item: make the units explicit
Keep pack size, stock units and price basis separate so an apparently cheaper supplier is not selected using incomparable values or rounded display prices.
Troubleshooting guide
Yesterday's supplier feed finishes last: keep older data from replacing a newer version
Compare source-issued versions at the publication boundary and distinguish a late old feed from an authorised correction to the current one.
Troubleshooting guide
Supplier adds a CSV column: reject header drift before fields shift into the wrong place
Validate the declared header and every row's shape before mapping a supplier stock or price update, rather than accepting a successfully parsed but misaligned record.
Platform
PostgreSQL supplier-feed imports: validate the source contract before the upsert
For distributors with an existing PostgreSQL-backed application, separate product keys, feed meaning and publication policy from a database statement that merely accepts rows.
Buyer collection
For a distributor's operations owner: stop supplier-feed mistakes without a new inventory system
Name who approves product matching, units and feed exceptions, then request one testable local repair or one small review interaction in the application you already use.
Collection
Supplier stock and price import checks: choose the first failing boundary
A distributor-focused sequence from CSV shape through identity, field meaning, units and feed publication, linked to worked synthetic cases and narrowly eligible paid enquiries.