Direct Escalation: Encountering an issue with time-driven triggers, alert delivery, or schema formatting? Fill out the generator below to send a structured diagnostic report to our core engineering team at [email protected].
Interactive Bug Report Generator
Complete this form to generate a structured bug ticket. You can launch your mail client directly or copy the formatted report to your clipboard:
How to Collect Diagnostic Telemetry
Providing diagnostic telemetry drastically speeds up resolution. Follow these steps to obtain diagnostic context:
1
Inspect System Health in the Control Panel
Inside your Google Sheet, select:
Extensions > SheetsDuty > Launch Control Panel
Check the sidebar indicators and manual controls:
- Presence and integrity of the core schema tabs (_INCIDENTS, _MONITORS, _ALERTS).
- System Health statistics (Active Monitors count, License Tier badge, Open Incident count).
- Click Run Self-Healing under Manual Controls to verify schema integrity.
- Click Ping All Monitors Now to check edge connectivity.
2
Copy Error Messages or Console Logs
If an execution error occurs, copy the error message or browser console logs and paste them into the Diagnostic Output field above.
Severity Guidelines
| Level | Classification | Definition & Impact |
|---|---|---|
| P1 | Critical Outage | Global monitoring is non-functional, false uptime alerts triggered, or critical security vulnerability. |
| P2 | High Severity | Escalation handoff fails to notify backup responders, or email delivery delayed > 5 minutes. |
| P3 | Medium Severity | Sidebar layout glitch, non-critical formula display warning, or cosmetic rendering error. |
| P4 | Low / Suggestion | Minor styling, feature enhancement ideas, documentation typo. |
Security Vulnerability & Responsible Disclosure Policy
Responsible Disclosure: We take security vulnerabilities with utmost seriousness. If you believe you have discovered a vulnerability in SheetsDuty (such as SSRF bypass, formula injection escaping, or authentication replay), please contact us responsibly.
Please email details to [email protected] with the subject line [SECURITY VULNERABILITY].
- Provide detailed proof-of-concept steps to reproduce the vulnerability.
- Allow reasonable time for remediation before any public disclosure.
- Do not access or modify data belonging to other users or spreadsheets.
- We adhere to safe harbor guidelines: We will not initiate legal action against researchers acting in good faith who respect user privacy and report issues responsibly.