Troubleshoot Circuit From Symptom Readings
Have voltage, current or waveform readings from a prototype circuit and need likely causes plus the next checks to run.
Prompts for your job
Have voltage, current or waveform readings from a prototype circuit and need likely causes plus the next checks to run.
Have symptoms and recent changes and want a ranked list of likely causes and next checks.
Need to diagnose and resolve recurring problems users report with your project management tools.
Need to resolve a signing problem and find compliant options.
Have a field report or photos of concrete cracking and need likely causes, confirmation checks and next steps.
Use this when records are not syncing between your CRM and another system and you have an error message or log line to work from.
Use this when an experiment shows no data and you can describe the setup for likely causes.
Use this when a customer describes a problem in their own words and you need to identify likely causes and next steps.
Need to diagnose and resolve problems in database replication, such as network issues, configuration errors, or constraint violations.
Are encountering issues or unexpected behavior while implementing a specific design pattern.
Hear a customer describe an online or mobile banking problem and need step-by-step help.
Need a structured path to diagnose and fix a DNS problem.
Encounter a technical error in your drawing software and need troubleshooting steps based on the error message or behavior.
Need to diagnose and resolve EIGRP problems like neighbor adjacency failures or route inconsistencies.
Use this when an employee reports that their enrollment is wrong, such as the wrong plan, a missing dependent, or an unexpected deduction.
Have a written description of team tension and need possible causes and next steps.
Use this when an ERP user reports a confusing issue during post-go-live support and you need clear diagnostic steps rather than guesswork.
Have a payload or exploit failing and need possible causes and next troubleshooting steps from the error text.
Have a superintendent's description of a field problem and need likely causes and next steps.
Have a finish with bubbles, streaks, or uneven color and need possible causes and next steps.
Use this when someone reports a vague problem such as 'the app is slow since Tuesday' and you need a focused set of questions and tests.
Hit an export error, a rejected file, or a print that does not match your artwork and need a structured way to find the cause.
Use this when a machine or assay gives an error message or odd result and you want a checklist of likely causes.
Need to diagnose and resolve connectivity or performance issues in your IoT network.