From software problem to a clear next step.
Choose a topic and what you need to do next. Add a search phrase to find a specific problem.
Browse 20 topics
Explore the playbooks
1500 guides · Page 27 of 60
-
Triage Ambiguous Retries After Partial Imports
Reconcile accepted, rejected, and unknown row outcomes before deciding whether a retry will repeat completed work or safely address only failed records.
-
Prioritize Unsafe Partial Import Retry Flows
Assess retry ambiguity by repeated accepted work, unresolved row outcomes, recovery burden, and whether users can see the next attempt’s exact scope.
-
Investigate Partial Import Retry Selection
Trace per-row outcomes, source identity, corrected files, and attempt linkage to reproduce why completed records are selected again or failed rows disappear.
-
Verify Retry Scope After a Partial Import
Check mixed success and failure, corrected rows, repeated attempts, and exact destination outcomes so retry handles only the work users intend to repeat.
-
Make Partial Import Recovery Easier Next Time
Preserve the row-outcome and retry-selection contract so future recovery changes keep accepted work, corrected records, and unknown outcomes distinguishable.
-
Triage Misleading Import Error Locations
Map a reported validation error back to its source record and column to distinguish numbering, header offsets, multiline records, and mapping-label confusion.
-
Prioritize Unusable Import Validation Messages
Rank misleading error locations by blocked correction, repeated uploads, risk of editing the wrong record, and the quality of alternative source references.
-
Investigate Row and Column Locations in Import Errors
Trace source coordinates through parsing, normalization, mapping, and validation to find where a useful error location becomes offset or mislabeled.
-
Verify Import Errors Point to the Correct Source
Check error coordinates and correction flows across headers, multiline fields, mapped labels, and multiple rejected records using independent source references.
-
Keep Import Error Coordinates Useful as Flows Change
Document source-location semantics and preserve fixtures that expose header offsets, multiline counting, mapping labels, and correction-path drift.
-
Triage Unexpected Blank Rows in Imports
Distinguish blank lines, empty-field records, whitespace, and quoted newlines to locate why an import adds or skips unexpected records.
-
Prioritize Inconsistent Blank-Row Import Behavior
Assess blank-row handling by lost records, unexpected empty entries, misleading counts, correction difficulty, and affected source-file conventions.
-
Investigate Blank-Line and Empty-Record Imports
Compare source structures and skip rules across parsing, validation, counts, and error coordinates without deleting meaningful quoted content.
-
Verify Blank Rows and Empty Records During Import
Check supported blank structures, leading and trailing positions, record counts, multiline values, and source error locations against explicit expectations.
-
Keep Blank-Row Import Rules Consistent
Document blank structure semantics and retain fixtures that expose skipped records, unwanted empty entries, altered multiline text, and shifted error locations.
-
Triage Incorrect Boolean Values After Import
Compare source tokens with documented accepted values and stored state to locate unintended truthiness, case handling, or blank-value defaults.
-
Prioritize Boolean Parsing Errors in Imports
Assess unintended true or false assignments by changed workflow behavior, silent defaults, affected tokens, preview clarity, and recovery confidence.
-
Investigate Boolean Token Conversion During Import
Trace explicit true and false tokens, whitespace, case, blanks, and invalid inputs through normalization, parsing, defaults, and field assignment.
-
Verify Boolean Import Values and Invalid Tokens
Check supported true and false representations, normalization, blank behavior, rejected tokens, persisted state, and a representative downstream use.
-
Keep Boolean Import Semantics Explicit
Maintain a token contract and contrasting fixtures so normalization, defaults, and new export formats cannot silently change imported true and false values.
-
Triage Spreadsheet Dates That Import Incorrectly
Compare displayed dates, exported source values, date-system assumptions, and stored results to locate serial-value or ambiguous-format interpretation errors.
-
Prioritize Incorrect Spreadsheet Date Imports
Assess date interpretation problems by shifted scheduling or reporting, silent acceptance, affected export formats, and the ability to recover the intended date.
-
Investigate Serial and Formatted Spreadsheet Dates
Trace exported values, source date-system context, parsing rules, and destination date types with fixtures that distinguish competing interpretations.
-
Verify Spreadsheet Dates Survive an Import
Check supported serial and text formats, ambiguous dates, preview settings, stored calendar values, and timestamp boundaries with known expected dates.
-
Keep Spreadsheet Date Import Assumptions Visible
Document supported date representations and preserve known-date fixtures that expose serial-system assumptions, ambiguous formats, and later calendar shifts.