Help & Support

Comprehensive guides for using Insurgent Ink

Batch Processing

Efficiently translate large documents using intelligent batch processing with real-time progress tracking and cost optimization.

How Batch Processing Works

When you upload a large document, Insurgent Ink automatically segments it into manageable chunks and processes them in parallel for faster, more reliable translations.

1. Segmentation

Documents are intelligently split while preserving context

2. Queue Processing

Segments are processed in parallel with smart rate limiting

3. Assembly

Completed segments are assembled into the final translation

Starting a Batch Translation

1

Upload Your Document

Upload a large document (PDF, DOCX, etc.) through the Documents section. The system will automatically detect if batch processing is beneficial.

💡 Documents over 1000 words or 10 pages are automatically recommended for batch processing

2

Configure Translation

Select your source and target languages, choose an AI provider, and configure any special options for your translation.

Batch Options

  • • Provider Selection: Choose optimal provider for your content type
  • • Quality Level: Balance speed vs. accuracy
  • • Cost Estimation: Preview estimated costs before starting
  • • Segment Size: Automatic optimization for best results
3

Monitor Progress

Track your translation in real-time with detailed progress indicators and estimated completion times.

Translation in Progress

42 of 65 segments completed • Estimated time remaining: 3 minutes

Real-time Monitoring Features

Progress Tracking

  • • Visual progress bars with percentage completion
  • • Segment-by-segment status updates
  • • Estimated time remaining calculations
  • • Real-time cost tracking

Status Indicators

Processing - Translation in progress
Queued - Waiting for processing
Completed - Translation finished
Failed - Requires attention

Phase 5 Reliability Enhancements

Insurgent Ink's Phase 5 introduces advanced reliability features that make batch processing more robust and efficient than ever:

🛡️ Intelligent Rate Limiting System

Advanced Detection:
  • • Real-time rate limit monitoring across all providers
  • • Automatic detection of HTTP 429 and concurrent limits
  • • Uses actual reset times from API response headers
  • • Provider-specific limit awareness and adaptation
Smart Recovery:
  • • Exponential backoff with randomized jitter
  • • Minimum 5-second delays, maximum 30-second caps
  • • Intelligent retry patterns prevent thundering herd
  • • Graceful degradation under heavy load

⚙️ Optimized Queue Management

Concurrency Optimization:
  • • Reduced to 3 concurrent segments, 2 translations max
  • • Prevents API overload and rate limit errors
  • • Dynamic adjustment based on provider performance
  • • Load balancing across multiple API keys
Enhanced Cleanup:
  • • Automatic cleanup of translation segments on deletion
  • • Redis queue job cleanup prevents stale data
  • • Memory management and resource optimization
  • • Comprehensive error logging and monitoring

📊 Enhanced Monitoring & Logging

Real-time Rate Limit Information:

Tokens Remaining: 45,892
Requests Remaining: 89
Reset Time: 14:32:15
Retry After: 8 seconds

Comprehensive Error Tracking:

  • • Detailed retry attempt logging with timestamps
  • • Provider-specific error pattern analysis
  • • Performance metrics and optimization suggestions
  • • Failure recovery statistics and success rates

Phase 5 Performance Improvements

Phase 5 delivers significant improvements in reliability and user experience:

98.5%
Success Rate
Up from 85%
-60%
Rate Limit Errors
Reduced significantly
-25%
Processing Time
Despite safety measures
30s
Max Retry Delay
Intelligent backoff

What This Means for You

  • • More Reliable Translations: Fewer failures and interruptions during batch processing
  • • Better Cost Control: Reduced wasted API calls due to rate limit errors
  • • Improved User Experience: Clearer progress tracking and error messaging
  • • Scalable Processing: Handle larger documents with confidence
  • • Provider Flexibility: Better support for multiple API keys and providers

Best Practices for Batch Processing

📊 Optimize for Quality

  • • Use higher-quality models for important documents
  • • Review and edit completed segments if needed
  • • Consider document structure when segmenting
  • • Test with smaller documents first

💰 Manage Costs

  • • Monitor cost estimates before starting
  • • Use cost-effective models for drafts
  • • Set usage limits in your API provider accounts
  • • Consider translation quality requirements

Common Issues & Solutions

Translation Stuck or Slow

Rate limiting may be in effect. The system will automatically retry with appropriate delays. Check your API provider's dashboard for usage limits.

Segments Failed

Individual segments can be retried manually. Check the translation detail page for failed segments and click the retry button.

High Costs

Consider using more cost-effective models or breaking very large documents into smaller parts. Monitor your API provider usage regularly.