Review & troubleshooting
Keep a useful troubleshooting note
Record enough context to solve a problem without copying private client data everywhere.
By LoopLily · 1 min read
Describe the expected behavior
Write what should have happened, which kind of workflow was involved, and the relevant time period. Use a fictional or internal reference instead of spreading a full client name and address into every note. A precise expectation is more useful than ‘the email is broken.’
Record what you observed
Note the automation’s state, the relevant record fields, Gmail readiness, and the log result. Distinguish facts from guesses. If you changed a setting, record the change and the reason so you can tell whether it affected the next attempt.
Protect the evidence
When sharing screenshots for support or documentation, inspect account details, recipient addresses, preference links, and browser chrome. Remove identifying information that is not needed to explain the issue. Keep the note focused on the workflow and outcome. This makes troubleshooting easier to hand off while reducing confusion caused by incomplete screenshots or undocumented trial-and-error changes.