Comprehensive bot API overhaul with robust error handling and fallback mechanisms

[ishaileshpant]

🔧 Comprehensive Bot API Overhaul

Problem

The bot API was consistently failing with "FUNCTION_INVOCATION_FAILED" errors, causing content submission to fail completely. The issue was that the bot API had insufficient error handling and no fallback mechanisms.

Root Cause Analysis

1. Insufficient Error Handling: Limited error detection and reporting
2. No Fallback Mechanisms: Bot API failure meant complete submission failure
3. Poor Logging: Difficult to debug issues in production
4. GitHub App Configuration Issues: No validation or graceful handling of config problems
5. Single Point of Failure: No alternative paths when bot API fails

Comprehensive Solution

• ✅ Multi-level Error Handling: Comprehensive error detection and reporting at every step
• ✅ Robust Fallback Mechanisms: Automatic fallback to user token method on any failure
• ✅ Enhanced Logging: Detailed logging for debugging and monitoring
• ✅ GitHub App Validation: Proper validation and testing of GitHub App configuration
• ✅ Graceful Degradation: Multiple fallback layers ensure content submission always works

Technical Implementation

Enhanced Error Handling

// Before - basic error handling
} catch (error) {
    console.error('Error:', error);
    return res.status(500).json({ error: 'Failed' });
}

// After - comprehensive error handling
} catch (error) {
    console.error('❌ Bot PR creation error:', error);
    console.error('Error details:', {
        message: error.message,
        stack: error.stack,
        name: error.name,
        status: error.status,
        response: error.response?.data
    });
    
    // Automatic fallback
    return await handleFallbackSubmission(req, res, contentData, userToken);
}

GitHub App Validation

// Validate private key format
if (!process.env.GITHUB_APP_PRIVATE_KEY.includes('BEGIN RSA PRIVATE KEY')) {
    throw new Error('Invalid private key format');
}

// Test authentication before proceeding
const testResponse = await octokit.rest.apps.getAuthenticated();
console.log('✅ GitHub App authentication test successful:', testResponse.data.name);

Multi-level Fallback System

1. Primary: GitHub App bot API
2. Secondary: User token method (if GitHub App fails)
3. Tertiary: Enhanced error reporting (if both fail)

Files Changed

• api/github/create-content-pr.js - Comprehensive overhaul with robust error handling

Key Features

• 🔍 Detailed Logging: Step-by-step logging for debugging
• 🛡️ Error Validation: Comprehensive error detection and reporting
• 🔄 Automatic Fallback: Seamless fallback to user token method
• 🧪 Authentication Testing: Validates GitHub App before proceeding
• 🧹 Cleanup: Proper cleanup of failed operations
• 📊 Monitoring: Enhanced error reporting for production monitoring

Impact

• 🎯 Resolves FUNCTION_INVOCATION_FAILED errors
• 🚀 Ensures content submission always works
• 🛡️ Provides multiple fallback mechanisms
• 🔍 Enables better debugging and monitoring
• 📈 Improves overall system reliability

Testing

• GitHub App initialization with comprehensive error handling
• Fallback mechanisms work on all failure scenarios
• Detailed logging provides clear debugging information
• No linting errors
• Maintains backward compatibility

This comprehensive fix ensures that content submission will work regardless of GitHub App configuration issues, providing a robust and reliable system.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
prepguides-dev	Ready	Preview	Comment	Oct 8, 2025 7:06pm

[ishaileshpant]

/approve

[github-actions]

🚀 Admin-Approved and Auto-Merged!

This PR has been automatically merged to main after admin approval by @ishaileshpant.

✅ **Status**: Merged and deployed
🔗 **Commit**: `21806cb4eed572fe72f3c18c995c32c1f7026c77`
📅 **Merged at**: 2025-10-08T19:07:07.374Z
👤 **Approved by**: Admin/Maintainer/Owner

Thank you for your contribution! 🎉