Official Documentation Debugging
When debugging, skipping steps is the biggest risk. The value of official documentation is that it gives you a fixed sequence: start with the desktop app, then check the address, then the access code, then the request content.
A Real Scenario
Section titled “A Real Scenario”If you’ve already tried several tools and all of them failed, go back to the minimal request in the official documentation first to confirm the interface itself is working.
How to Decide What to Do Next
Section titled “How to Decide What to Do Next”| Your Situation | What to Check First | Next Step | | --- | --- | --- | | Not sure where to start | Current page title and main entry point | Pick only the item related to your current goal | | Result is wrong after an action | Status, empty prompts, access history, or sync progress | Go back one level and troubleshoot in order | | Worried about affecting data | Backup, sync, account, or permissions documentation | Stop first, confirm your scope, then continue |
Boundaries
Section titled “Boundaries”Once the minimal reproducible request passes, go back to your specific tool configuration. This makes it easier to pinpoint the problem.
Next Step
Section titled “Next Step”After reading this section, return to the task you are working on. Pick only one minimal action to continue: log an input, check a status, or open relevant settings to complete a confirmation.