BabelizeBabelize
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

  1. Known issues: Check recent changelog
  2. Status page: Verify at status.babelize.app
  3. Troubleshooting: Try common fixes
  4. 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:

How to Report

Via Dashboard

  1. Click the Help button in the dashboard
  2. Select Report a Bug
  3. Fill out the bug report form
  4. Submit

Via Email

Email: bugs@babelize.app

What to Include

Essential Information

InformationWhy We Need It
DescriptionWhat went wrong
Steps to reproduceHow to recreate the issue
Expected behaviorWhat should happen
Actual behaviorWhat actually happened
Account emailTo 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

  1. Acknowledgment: You'll receive confirmation
  2. Triage: We assess severity and priority
  3. Investigation: We reproduce and diagnose
  4. Update: We'll inform you of progress
  5. 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.

On this page