Help
Report a Bug
How to report bugs and issues in Babelize.
Report a Bug
Found something broken? Help us fix it by submitting a bug report.
Before Reporting
Check First
- Known issues: Check recent changelog
- Status page: Verify at status.babelize.app
- Troubleshooting: Try common fixes
- Existing reports: Search for similar issues
Determine if It's a Bug
Is a bug:
- Something that used to work now doesn't
- Feature behaving differently than documented
- Error messages when performing normal actions
- Data loss or corruption
Not a bug:
- Feature requests → Submit here
- How-to questions → Check FAQ
- Account issues → Contact support
How to Report
Via Dashboard
- Click the Help button in the dashboard
- Select Report a Bug
- Fill out the bug report form
- Submit
Via Email
Email: bugs@babelize.app
What to Include
Essential Information
| Information | Why We Need It |
|---|---|
| Description | What went wrong |
| Steps to reproduce | How to recreate the issue |
| Expected behavior | What should happen |
| Actual behavior | What actually happened |
| Account email | To investigate your account |
Helpful Additions
- Screenshots/recordings: Visual evidence
- Browser/OS: Your environment
- Job/Project ID: For translation issues
- Error messages: Exact text
- Timestamp: When it occurred
Example Bug Report
Subject: Translation fails for large YAML files
Description:
YAML files over 500KB fail with a timeout error, even though my plan
allows 1MB files.
Steps to reproduce:
1. Upload a YAML file larger than 500KB
2. Configure English to Spanish translation
3. Click Translate
4. Wait ~60 seconds
Expected behavior:
Translation should complete successfully
Actual behavior:
Error message: "Translation timed out. Please try again."
Environment:
- Browser: Chrome 120.0 on Windows 11
- Account: user@example.com
- File: config.yaml (683KB)
- Project: proj_abc123
This started happening about 2 days ago. Smaller files work fine.Bug Severity
Critical
- Service completely unavailable
- Data loss
- Security vulnerability
Response: Immediate investigation
High
- Major feature broken
- Workaround difficult or impossible
- Affects many users
Response: Same business day
Medium
- Feature partially broken
- Workaround available
- Limited impact
Response: Within 3 business days
Low
- Minor inconvenience
- UI/cosmetic issues
- Rare edge cases
Response: Scheduled for future fix
After Reporting
What Happens Next
- Acknowledgment: You'll receive confirmation
- Triage: We assess severity and priority
- Investigation: We reproduce and diagnose
- Update: We'll inform you of progress
- Resolution: Bug fixed or workaround provided
Tracking Your Report
- Bug reports receive a ticket ID
- Check status via reply to confirmation email
- Major bugs noted in changelog
Security Vulnerabilities
For security issues, use responsible disclosure:
Email: security@babelize.app
Do not publicly disclose vulnerabilities before they're fixed.
We offer:
- Acknowledgment within 24 hours
- Credit in security acknowledgments
- Good-faith protection for responsible disclosure
Bug Bounty
We're planning a bug bounty program. Currently, we recognize security researchers in our acknowledgments.
Feedback on Fixes
Once we fix your bug:
- Verify the fix works for you
- Reply if the issue persists
- Let us know if it's fully resolved
Your confirmation helps us close issues confidently.