ikk

APSCHEDULER_ANALYSIS_SUMMARY.md

@@ -0,0 +1,198 @@
+# APScheduler Analysis Summary
+
+## Problem Diagnosis
+
+### Issue Description
+The user reported that when starting their Lin application, they don't see any output from the APS scheduler in the startup logs. The application starts successfully on port 7860, but there are no scheduler-related messages visible.
+
+### Root Cause Analysis
+After analyzing the code and startup logs, I identified the following issues:
+
+1. **Missing Logging Configuration**: The APScheduler logger is not configured to show debug messages. According to APScheduler documentation, you need to explicitly configure logging for the 'apscheduler' logger to see its output.
+
+2. **No Startup Verification**: There are no explicit verification messages to confirm that APScheduler is initialized and working.
+
+3. **Silent Operation**: APScheduler is working in the background but operates silently without visible feedback.
+
+## Current State Assessment
+
+### What's Working ✅
+- Flask application starts successfully on port 7860
+- APScheduler is properly imported and initialized in `backend/app.py`
+- Scheduler service is correctly configured with logging statements
+- Database integration is properly set up
+- Job creation and execution mechanisms are in place
+
+### What's Missing ❌
+- APScheduler debug messages are not visible in startup logs
+- No startup verification messages
+- No feedback about scheduler status or job counts
+- Logging configuration not properly set up for APScheduler
+
+## Solution Architecture
+
+### Phase 1: Logging Configuration
+**Target File**: `backend/app.py`
+**Changes Required**:
+```python
+import logging
+
+# Configure logging for APScheduler
+logging.basicConfig(
+    level=logging.DEBUG,
+    format='%(asctime)s - %(name)s - %(levelname)s - %(message)s'
+)
+logging.getLogger('apscheduler').setLevel(logging.DEBUG)
+```
+
+### Phase 2: Startup Verification
+**Target File**: `backend/app.py`
+**Changes Required**:
+Add verification messages after APScheduler initialization:
+```python
+# Verify APScheduler initialization
+if hasattr(app, 'scheduler') and app.scheduler.scheduler is not None:
+    app.logger.info("✅ APScheduler initialized successfully")
+    app.logger.info(f"📊 Current jobs: {len(app.scheduler.scheduler.get_jobs())}")
+    app.logger.info("🔄 Schedule loading job added (runs every 5 minutes)")
+else:
+    app.logger.warning("⚠️ APScheduler initialization failed")
+```
+
+### Phase 3: Testing Infrastructure
+**New Files to Create**:
+- `test_scheduler_visibility.py` - Standalone test script
+- `test_scheduler_integration.py` - Integration test script
+
+### Phase 4: Documentation Updates
+**Files to Update**:
+- `APSCHEDULER_SETUP.md` - Add troubleshooting section
+- Create comprehensive test plan and implementation guide
+
+## Expected Results
+
+### Before Fix
+```
+Starting Lin application on port 7860...
+============================================================
+============================================================
+Flask application starting...
+Access the application at:
+  http://localhost:7860
+  http://127.0.0.1:7860
+============================================================
+ * Serving Flask app 'backend.app'
+ * Debug mode: off
+INFO:werkzeug:WARNING: This is a development server...
+```
+
+### After Fix
+```
+Starting Lin application on port 7860...
+============================================================
+============================================================
+Flask application starting...
+Access the application at:
+  http://localhost:7860
+  http://127.0.0.1:7860
+============================================================
+ * Serving Flask app 'backend.app'
+ * Debug mode: off
+INFO:werkzeug:WARNING: This is a development server...
+INFO:backend.app:Initializing APScheduler...
+INFO:backend.apscheduler_service:Initializing APScheduler...
+INFO:backend.apscheduler_service:Initializing Supabase client...
+INFO:backend.apscheduler_service:Supabase client initialized
+INFO:backend.apscheduler_service:Creating BackgroundScheduler...
+INFO:backend.apscheduler_service:BackgroundScheduler created
+INFO:backend.apscheduler_service:Starting scheduler...
+INFO:backend.apscheduler_service:Scheduler started
+INFO:backend.apscheduler_service:Adding periodic job to load schedules...
+INFO:backend.apscheduler_service:Periodic job added
+INFO:backend.apscheduler_service:Loading schedules immediately...
+INFO:backend.apscheduler_service:Found 0 schedules in database
+INFO:backend.apscheduler_service:Updated APScheduler schedule
+INFO:backend.app:✅ APScheduler initialized successfully
+INFO:backend.app:📊 Current jobs: 1
+INFO:backend.app:🔄 Schedule loading job added (runs every 5 minutes)
+```
+
+## Implementation Plan
+
+### Step 1: Configure Logging
+- Add logging configuration to `backend/app.py`
+- Ensure APScheduler logger is set to DEBUG level
+- Test that messages now appear in logs
+
+### Step 2: Add Verification
+- Add startup verification messages
+- Include job count information
+- Add clear success/failure indicators
+
+### Step 3: Create Test Scripts
+- Create standalone test script for verification
+- Create integration test for Flask app
+- Document usage and expected outputs
+
+### Step 4: Update Documentation
+- Update setup guide with troubleshooting section
+- Add logging configuration instructions
+- Document test procedures
+
+## Risk Assessment
+
+### Low Risk Changes
+- Logging configuration (no functional changes)
+- Startup verification messages (no functional changes)
+- Test scripts (standalone, don't affect production)
+
+### Medium Risk Changes
+- Any modifications to `backend/app.py` require careful testing
+
+### Mitigation Strategies
+1. **Backup**: Create backup of `backend/app.py` before changes
+2. **Testing**: Run test scripts after each change
+3. **Rollback**: Have rollback plan ready
+4. **Validation**: Verify application still starts and functions normally
+
+## Success Criteria
+
+The solution is successful when:
+
+1. ✅ APScheduler messages are visible in startup logs
+2. ✅ Startup verification messages appear
+3. ✅ Test scripts pass successfully
+4. ✅ Application continues to function normally
+5. ✅ No new errors are introduced
+6. ✅ Documentation is updated and accurate
+
+## Next Steps
+
+1. **Approve Implementation Plan** - Review and approve the proposed changes
+2. **Switch to Code Mode** - Move to implementation phase
+3. **Execute Changes** - Implement logging configuration and verification
+4. **Test Solution** - Run test scripts to verify functionality
+5. **Validate Results** - Confirm APScheduler output is now visible
+6. **Update Documentation** - Finalize documentation updates
+
+## Files Created/Modified
+
+### Created
+- `APSCHEDULER_VISIBILITY_FIX.md` - Comprehensive fix plan
+- `APSCHEDULER_TEST_PLAN.md` - Detailed test plan with scripts
+- `APSCHEDULER_ANALYSIS_SUMMARY.md` - This analysis summary
+
+### To Be Modified
+- `backend/app.py` - Add logging configuration and verification
+- `APSCHEDULER_SETUP.md` - Update with troubleshooting section
+
+## Conclusion
+
+The APScheduler is functional but not visible due to missing logging configuration. The solution is straightforward and low-risk, involving primarily logging configuration and verification messages. Once implemented, users will be able to see APScheduler activity in their logs, making it easier to monitor and debug scheduling issues.
+
+The implementation will provide:
+- Clear visibility into APScheduler operations
+- Better debugging capabilities
+- Improved user experience
+- Comprehensive testing infrastructure
+- Updated documentation for future reference

APSCHEDULER_TEST_PLAN.md

@@ -0,0 +1,462 @@
+# APScheduler Test Plan
+
+## Overview
+
+This document outlines a comprehensive test plan to verify APScheduler functionality and visibility in the Lin application. The plan includes both automated tests and manual verification steps.
+
+## Test Objectives
+
+1. **Verify APScheduler is properly initialized** during application startup
+2. **Confirm logging configuration** shows APScheduler messages
+3. **Test schedule loading functionality** from the database
+4. **Verify job creation and execution** mechanisms
+5. **Ensure scheduler persistence** and error handling
+
+## Test Environment Setup
+
+### Prerequisites
+- Python 3.8+ installed
+- All dependencies from `backend/requirements.txt` installed
+- Environment variables configured (Supabase credentials, etc.)
+- Access to the Lin application source code
+
+### Test Files to Create
+
+#### 1. `test_scheduler_visibility.py`
+**Purpose**: Standalone test script to verify APScheduler logging and basic functionality
+
+```python
+#!/usr/bin/env python3
+"""
+Test script for APScheduler visibility and functionality.
+This script tests whether APScheduler is working and properly configured for logging.
+"""
+
+import sys
+import os
+import logging
+from pathlib import Path
+from datetime import datetime
+
+# Add the backend directory to the Python path
+backend_dir = Path(__file__).parent / "backend"
+sys.path.insert(0, str(backend_dir))
+
+def setup_logging():
+    """Setup logging for the test script."""
+    logging.basicConfig(
+        level=logging.DEBUG,
+        format='%(asctime)s - %(name)s - %(levelname)s - %(message)s'
+    )
+    # Configure APScheduler logger specifically
+    logging.getLogger('apscheduler').setLevel(logging.DEBUG)
+    print("🔧 Logging configured for APScheduler")
+
+def test_apscheduler_import():
+    """Test that APScheduler can be imported."""
+    try:
+        from backend.scheduler.apscheduler_service import APSchedulerService
+        print("✅ APSchedulerService imported successfully")
+        return True
+    except Exception as e:
+        print(f"❌ Failed to import APSchedulerService: {e}")
+        return False
+
+def test_scheduler_initialization():
+    """Test APScheduler initialization with mock app."""
+    try:
+        from backend.scheduler.apscheduler_service import APSchedulerService
+        
+        # Create a mock app object
+        class MockApp:
+            def __init__(self):
+                self.config = {
+                    'SUPABASE_URL': 'https://test.supabase.co',
+                    'SUPABASE_KEY': 'test_key',
+                    'SCHEDULER_ENABLED': True
+                }
+        
+        # Initialize the scheduler service
+        app = MockApp()
+        scheduler_service = APSchedulerService()
+        
+        # Mock the Supabase client initialization
+        class MockSupabaseClient:
+            def table(self, table_name):
+                return self
+                
+            def select(self, columns):
+                return self
+                
+            def execute(self):
+                # Return empty schedule data for testing
+                return type('obj', (object,), {'data': []})()
+        
+        scheduler_service.supabase_client = MockSupabaseClient()
+        
+        # Test initialization
+        scheduler_service.init_app(app)
+        
+        if scheduler_service.scheduler is not None:
+            print("✅ APScheduler initialized successfully")
+            print(f"📊 Current jobs: {len(scheduler_service.scheduler.get_jobs())}")
+            return True
+        else:
+            print("❌ APScheduler initialization failed")
+            return False
+            
+    except Exception as e:
+        print(f"❌ Error testing APScheduler initialization: {e}")
+        import traceback
+        traceback.print_exc()
+        return False
+
+def test_schedule_loading():
+    """Test the schedule loading functionality."""
+    try:
+        from backend.scheduler.apscheduler_service import APSchedulerService
+        
+        # Create scheduler service
+        scheduler_service = APSchedulerService()
+        
+        # Mock the Supabase client
+        class MockSupabaseClient:
+            def table(self, table_name):
+                return self
+                
+            def select(self, columns):
+                return self
+                
+            def execute(self):
+                # Return mock schedule data
+                mock_data = [
+                    {
+                        'id': 'test_schedule_1',
+                        'schedule_time': 'Monday 09:00',
+                        'adjusted_time': 'Monday 08:55',
+                        'Social_network': {
+                            'id_utilisateur': 'test_user_1',
+                            'token': 'test_token',
+                            'sub': 'test_sub'
+                        }
+                    }
+                ]
+                return type('obj', (object,), {'data': mock_data})()
+        
+        scheduler_service.supabase_client = MockSupabaseClient()
+        
+        # Test schedule loading
+        scheduler_service.load_schedules()
+        
+        if scheduler_service.scheduler is not None:
+            jobs = scheduler_service.scheduler.get_jobs()
+            print(f"✅ Schedule loading test completed")
+            print(f"📊 Total jobs: {len(jobs)}")
+            
+            # Check for specific job types
+            loader_jobs = [job for job in jobs if job.id == 'load_schedules']
+            content_jobs = [job for job in jobs if job.id.startswith('gen_')]
+            publish_jobs = [job for job in jobs if job.id.startswith('pub_')]
+            
+            print(f"🔄 Loader jobs: {len(loader_jobs)}")
+            print(f"📝 Content generation jobs: {len(content_jobs)}")
+            print(f"📤 Publishing jobs: {len(publish_jobs)}")
+            
+            return len(jobs) > 0
+        else:
+            print("❌ Scheduler not initialized for schedule loading test")
+            return False
+            
+    except Exception as e:
+        print(f"❌ Error testing schedule loading: {e}")
+        import traceback
+        traceback.print_exc()
+        return False
+
+def main():
+    """Main test function."""
+    print("🚀 Testing APScheduler visibility and functionality...")
+    print("=" * 60)
+    
+    setup_logging()
+    
+    tests = [
+        ("APScheduler Import", test_apscheduler_import),
+        ("Scheduler Initialization", test_scheduler_initialization),
+        ("Schedule Loading", test_schedule_loading),
+    ]
+    
+    passed = 0
+    total = len(tests)
+    
+    for test_name, test_func in tests:
+        print(f"\n📋 Running test: {test_name}")
+        print("-" * 40)
+        
+        if test_func():
+            passed += 1
+            print(f"✅ {test_name} PASSED")
+        else:
+            print(f"❌ {test_name} FAILED")
+    
+    print("\n" + "=" * 60)
+    print(f"📊 Test Results: {passed}/{total} tests passed")
+    
+    if passed == total:
+        print("🎉 All tests passed! APScheduler is working correctly.")
+        return True
+    else:
+        print("⚠️ Some tests failed. Please check the error messages above.")
+        return False
+
+if __name__ == "__main__":
+    success = main()
+    sys.exit(0 if success else 1)
+```
+
+#### 2. `test_scheduler_integration.py`
+**Purpose**: Test APScheduler integration with the actual Flask application
+
+```python
+#!/usr/bin/env python3
+"""
+Integration test for APScheduler with Flask application.
+Tests the actual application startup and scheduler initialization.
+"""
+
+import sys
+import os
+import subprocess
+import time
+from pathlib import Path
+
+def test_app_startup_with_scheduler():
+    """Test that the Flask application starts with APScheduler visible."""
+    try:
+        # Change to the project directory
+        project_dir = Path(__file__).parent
+        os.chdir(project_dir)
+        
+        # Start the application
+        print("🚀 Starting Flask application with APScheduler...")
+        process = subprocess.Popen(
+            [sys.executable, "start_app.py"],
+            stdout=subprocess.PIPE,
+            stderr=subprocess.STDOUT,
+            text=True,
+            bufsize=1,
+            universal_newlines=True
+        )
+        
+        # Wait for startup and capture output
+        startup_timeout = 30  # 30 seconds timeout
+        start_time = time.time()
+        
+        scheduler_found = False
+        while time.time() - start_time < startup_timeout:
+            output = process.stdout.readline()
+            if output:
+                print(output.strip())
+                
+                # Check for APScheduler initialization messages
+                if "Initializing APScheduler" in output:
+                    scheduler_found = True
+                    print("✅ APScheduler initialization message found!")
+                
+                # Check for successful startup
+                if "running on http" in output.lower():
+                    break
+        
+        # Terminate the process
+        process.terminate()
+        process.wait(timeout=10)
+        
+        if scheduler_found:
+            print("✅ APScheduler is visible during application startup")
+            return True
+        else:
+            print("❌ APScheduler messages not found in startup logs")
+            return False
+            
+    except Exception as e:
+        print(f"❌ Error testing app startup: {e}")
+        return False
+
+def main():
+    """Main integration test function."""
+    print("🔗 Testing APScheduler integration with Flask application...")
+    print("=" * 60)
+    
+    success = test_app_startup_with_scheduler()
+    
+    print("\n" + "=" * 60)
+    if success:
+        print("🎉 Integration test passed! APScheduler is working in the Flask app.")
+    else:
+        print("⚠️ Integration test failed. APScheduler may not be properly configured.")
+    
+    return success
+
+if __name__ == "__main__":
+    success = main()
+    sys.exit(0 if success else 1)
+```
+
+## Test Execution Steps
+
+### Step 1: Run Standalone Test
+```bash
+# Navigate to project directory
+cd /path/to/your/project
+
+# Run the standalone test
+python test_scheduler_visibility.py
+```
+
+**Expected Output**:
+```
+🚀 Testing APScheduler visibility and functionality...
+============================================================
+🔧 Logging configured for APScheduler
+
+📋 Running test: APScheduler Import
+----------------------------------------
+✅ APSchedulerService imported successfully
+✅ APScheduler Import PASSED
+
+📋 Running test: Scheduler Initialization
+----------------------------------------
+✅ APScheduler initialized successfully
+📊 Current jobs: 1
+✅ Scheduler Initialization PASSED
+
+📋 Running test: Schedule Loading
+----------------------------------------
+✅ Schedule loading test completed
+📊 Total jobs: 3
+🔄 Loader jobs: 1
+📝 Content generation jobs: 1
+📤 Publishing jobs: 1
+✅ Schedule Loading PASSED
+
+============================================================
+📊 Test Results: 3/3 tests passed
+🎉 All tests passed! APScheduler is working correctly.
+```
+
+### Step 2: Run Integration Test
+```bash
+# Run the integration test
+python test_scheduler_integration.py
+```
+
+**Expected Output**:
+```
+🔗 Testing APScheduler integration with Flask application...
+============================================================
+🚀 Starting Flask application with APScheduler...
+Starting Lin application on port 7860...
+============================================================
+============================================================
+Flask application starting...
+Access the application at:
+  http://localhost:7860
+  http://127.0.0.1:7860
+============================================================
+ * Serving Flask app 'backend.app'
+ * Debug mode: off
+INFO:backend.app:Initializing APScheduler...
+INFO:backend.apscheduler_service:Initializing APScheduler...
+INFO:backend.apscheduler_service:Initializing Supabase client...
+INFO:backend.apscheduler_service:Supabase client initialized
+INFO:backend.apscheduler_service:Creating BackgroundScheduler...
+INFO:backend.apscheduler_service:BackgroundScheduler created
+INFO:backend.apscheduler_service:Starting scheduler...
+INFO:backend.apscheduler_service:Scheduler started
+INFO:backend.apscheduler_service:Adding periodic job to load schedules...
+INFO:backend.apscheduler_service:Periodic job added
+INFO:backend.apscheduler_service:Loading schedules immediately...
+INFO:backend.apscheduler_service:Found 0 schedules in database
+INFO:backend.apscheduler_service:Updated APScheduler schedule
+INFO:backend.app:✅ APScheduler initialized successfully
+INFO:backend.app:📊 Current jobs: 1
+INFO:backend.app:🔄 Schedule loading job added (runs every 5 minutes)
+ * Running on all addresses (0.0.0.0)
+ * Running on http://127.0.0.1:7860
+ * Running on http://10.108.66.211:7860
+✅ APScheduler initialization message found!
+✅ APScheduler is visible during application startup
+
+============================================================
+🎉 Integration test passed! APScheduler is working in the Flask app.
+```
+
+## Manual Verification Steps
+
+### 1. Check Application Startup Logs
+After implementing the logging configuration, start your application and look for:
+- `Initializing APScheduler...`
+- `BackgroundScheduler created`
+- `Scheduler started`
+- `Adding periodic job to load schedules...`
+- `Schedule loading job added (runs every 5 minutes)`
+
+### 2. Verify Scheduler Functionality
+1. Create a schedule via the API
+2. Check logs for schedule loading messages
+3. Verify that individual jobs are created
+4. Monitor for job execution at scheduled times
+
+### 3. Test Error Handling
+1. Test with invalid Supabase credentials
+2. Test with missing environment variables
+3. Verify appropriate error messages are logged
+
+## Troubleshooting Guide
+
+### Common Issues and Solutions
+
+#### Issue 1: No APScheduler messages in logs
+**Solution**: Ensure logging configuration is added to `backend/app.py`:
+```python
+import logging
+logging.basicConfig(level=logging.DEBUG)
+logging.getLogger('apscheduler').setLevel(logging.DEBUG)
+```
+
+#### Issue 2: Scheduler initialization fails
+**Solution**: Check environment variables and Supabase connection:
+- Verify `SUPABASE_URL` and `SUPABASE_KEY` are set
+- Check network connectivity to Supabase
+- Verify database tables exist
+
+#### Issue 3: Jobs not executing
+**Solution**: 
+- Check that the application is running continuously
+- Verify job triggers are correctly configured
+- Check for any exceptions in job execution
+
+#### Issue 4: Test script fails
+**Solution**:
+- Ensure all dependencies are installed
+- Check Python path includes the backend directory
+- Verify mock data structure matches actual database schema
+
+## Success Criteria
+
+The APScheduler implementation is considered successful when:
+
+1. ✅ **Startup logs** show APScheduler initialization messages
+2. ✅ **Test scripts** pass all tests
+3. ✅ **Integration test** shows scheduler working in Flask app
+4. ✅ **Manual verification** confirms job creation and execution
+5. ✅ **Error handling** works appropriately
+6. ✅ **Documentation** is updated with troubleshooting guide
+
+## Next Steps
+
+1. **Approve this test plan**
+2. **Switch to Code mode** to implement the logging configuration
+3. **Create the test scripts** outlined in this plan
+4. **Execute the tests** to verify APScheduler visibility
+5. **Update documentation** with the final solution

APSCHEDULER_VISIBILITY_FIX.md

@@ -0,0 +1,170 @@
+# APScheduler Visibility Fix Plan
+
+## Problem Analysis
+
+Based on the provided startup logs and code analysis, the issue is that APScheduler is being initialized in your Flask application but its output is not visible. Here's what's happening:
+
+### Current State
+- ✅ Flask application starts successfully on port 7860
+- ✅ APScheduler is imported and initialized in `backend/app.py`
+- ✅ Scheduler service is properly configured with logging
+- ❌ **No APScheduler output visible in startup logs**
+- ❌ **No verification messages showing scheduler status**
+
+### Root Cause
+The APScheduler logger is not configured to show debug messages. According to APScheduler documentation, you need to explicitly configure logging for the 'apscheduler' logger to see its output.
+
+## Solution Implementation Plan
+
+### Phase 1: Configure APScheduler Logging
+
+**File to modify**: `backend/app.py`
+
+**Changes needed**:
+1. Add logging configuration at the beginning of the file
+2. Configure the 'apscheduler' logger to show DEBUG level messages
+3. Ensure Flask app logging is also properly configured
+
+**Code to add**:
+```python
+import logging
+
+# Configure logging for APScheduler
+logging.basicConfig(
+    level=logging.DEBUG,
+    format='%(asctime)s - %(name)s - %(levelname)s - %(message)s'
+)
+logging.getLogger('apscheduler').setLevel(logging.DEBUG)
+```
+
+### Phase 2: Add Startup Verification
+
+**File to modify**: `backend/app.py`
+
+**Changes needed**:
+1. Add explicit verification messages after APScheduler initialization
+2. Check if scheduler started successfully
+3. Log the number of jobs loaded
+
+**Code to add** (after line 131):
+```python
+    # Verify APScheduler initialization
+    if hasattr(app, 'scheduler') and app.scheduler.scheduler is not None:
+        app.logger.info("✅ APScheduler initialized successfully")
+        app.logger.info(f"📊 Current jobs: {len(app.scheduler.scheduler.get_jobs())}")
+        app.logger.info("🔄 Schedule loading job added (runs every 5 minutes)")
+    else:
+        app.logger.warning("⚠️ APScheduler initialization failed")
+```
+
+### Phase 3: Create Test Script
+
+**New file**: `test_scheduler_visibility.py`
+
+**Purpose**: 
+- Test APScheduler functionality independently
+- Verify logging configuration works
+- Create a test schedule to demonstrate functionality
+
+**Features**:
+- Standalone test script
+- Mock database for testing
+- Clear output showing scheduler activity
+- Cleanup of test jobs
+
+### Phase 4: Update Documentation
+
+**File to modify**: `APSCHEDULER_SETUP.md`
+
+**Additions needed**:
+1. Section on troubleshooting visibility issues
+2. Logging configuration instructions
+3. Test script usage guide
+4. Common issues and solutions
+
+## Implementation Steps
+
+### Step 1: Configure Logging
+1. Add logging configuration to `backend/app.py`
+2. Test that APScheduler messages now appear in logs
+
+### Step 2: Add Verification
+1. Add startup verification messages
+2. Ensure scheduler status is clearly reported
+
+### Step 3: Create Test Script
+1. Create `test_scheduler_visibility.py`
+2. Test the script to verify functionality
+3. Document usage instructions
+
+### Step 4: Update Documentation
+1. Update `APSCHEDULER_SETUP.md` with new troubleshooting section
+2. Add logging configuration guide
+3. Document the test script
+
+## Expected Results
+
+After implementing this plan, you should see:
+
+### Startup Logs
+```
+Starting Lin application on port 7860...
+============================================================
+============================================================
+Flask application starting...
+Access the application at:
+  http://localhost:7860
+  http://127.0.0.1:7860
+============================================================
+ * Serving Flask app 'backend.app'
+ * Debug mode: off
+INFO:werkzeug:WARNING: This is a development server...
+INFO:backend.app:Initializing APScheduler...
+INFO:backend.apscheduler_service:Initializing APScheduler...
+INFO:backend.apscheduler_service:Initializing Supabase client...
+INFO:backend.apscheduler_service:Supabase client initialized
+INFO:backend.apscheduler_service:Creating BackgroundScheduler...
+INFO:backend.apscheduler_service:BackgroundScheduler created
+INFO:backend.apscheduler_service:Starting scheduler...
+INFO:backend.apscheduler_service:Scheduler started
+INFO:backend.apscheduler_service:Adding periodic job to load schedules...
+INFO:backend.apscheduler_service:Periodic job added
+INFO:backend.apscheduler_service:Loading schedules immediately...
+INFO:backend.apscheduler_service:Found 0 schedules in database
+INFO:backend.apscheduler_service:Updated APScheduler schedule
+INFO:backend.app:✅ APScheduler initialized successfully
+INFO:backend.app:📊 Current jobs: 1
+INFO:backend.app:🔄 Schedule loading job added (runs every 5 minutes)
+```
+
+### Test Script Output
+```
+Testing APScheduler visibility...
+✅ APScheduler initialized successfully
+✅ Test schedule created
+✅ Test job added to scheduler
+📊 Current jobs: 2
+✅ Test job executed successfully
+✅ Test job removed
+✅ All tests passed!
+```
+
+## Troubleshooting Checklist
+
+If you still don't see APScheduler output after implementing this plan:
+
+1. ✅ Check that logging configuration is added to `backend/app.py`
+2. ✅ Verify that `SCHEDULER_ENABLED=True` in environment variables
+3. ✅ Check that APScheduler is properly imported and initialized
+4. ✅ Ensure no other logging configuration is overriding the settings
+5. ✅ Test with the standalone test script
+6. ✅ Check for any error messages in the logs
+
+## Next Steps
+
+1. **Approve this plan** - Review and approve the implementation plan
+2. **Switch to Code mode** - I'll implement the actual code changes
+3. **Test the solution** - Verify that APScheduler output is now visible
+4. **Document the fix** - Update documentation for future reference
+
+This plan will ensure that APScheduler is not only working but also clearly visible in your application logs, making it easier to monitor and debug scheduling issues.

backend/app.py

@@ -1,6 +1,7 @@
 import os
 import sys
 import locale
+import logging
 from flask import Flask, send_from_directory, request
 from flask_cors import CORS
 from flask_jwt_extended import JWTManager
@@ -8,6 +9,13 @@ from flask_jwt_extended import JWTManager
 import uuid
 from concurrent.futures import ThreadPoolExecutor
 
+# Configure logging for APScheduler
+logging.basicConfig(
+    level=logging.DEBUG,
+    format='%(asctime)s - %(name)s - %(levelname)s - %(message)s'
+)
+logging.getLogger('apscheduler').setLevel(logging.DEBUG)
+
 # Use relative import for the Config class to work with Hugging Face Spaces
 from backend.config import Config
 from backend.utils.database import init_supabase
@@ -125,6 +133,14 @@ def create_app():
             scheduler = APSchedulerService(app)
             app.scheduler = scheduler
             app.logger.info("APScheduler initialized successfully")
+            
+            # Verify APScheduler initialization
+            if hasattr(app, 'scheduler') and app.scheduler.scheduler is not None:
+                app.logger.info("✅ APScheduler initialized successfully")
+                app.logger.info(f"📊 Current jobs: {len(app.scheduler.scheduler.get_jobs())}")
+                app.logger.info("🔄 Schedule loading job added (runs every 5 minutes)")
+            else:
+                app.logger.warning("⚠️ APScheduler initialization failed")
         except Exception as e:
             app.logger.error(f"Failed to initialize APScheduler: {str(e)}")
             import traceback

test_scheduler_integration.py

@@ -0,0 +1,88 @@
+#!/usr/bin/env python3
+"""
+Integration test for APScheduler with Flask application.
+Tests the actual application startup and scheduler initialization.
+"""
+
+import sys
+import os
+import subprocess
+import time
+from pathlib import Path
+
+def test_app_startup_with_scheduler():
+    """Test that the Flask application starts with APScheduler visible."""
+    try:
+        # Change to the project directory
+        project_dir = Path(__file__).parent
+        os.chdir(project_dir)
+        
+        # Start the application
+        print("🚀 Starting Flask application with APScheduler...")
+        process = subprocess.Popen(
+            [sys.executable, "start_app.py"],
+            stdout=subprocess.PIPE,
+            stderr=subprocess.STDOUT,
+            text=True,
+            bufsize=1,
+            universal_newlines=True
+        )
+        
+        # Wait for startup and capture output
+        startup_timeout = 30  # 30 seconds timeout
+        start_time = time.time()
+        
+        scheduler_found = False
+        verification_found = False
+        while time.time() - start_time < startup_timeout:
+            output = process.stdout.readline()
+            if output:
+                print(output.strip())
+                
+                # Check for APScheduler initialization messages
+                if "Initializing APScheduler" in output:
+                    scheduler_found = True
+                    print("✅ APScheduler initialization message found!")
+                
+                # Check for verification messages
+                if "✅ APScheduler initialized successfully" in output:
+                    verification_found = True
+                    print("✅ APScheduler verification message found!")
+                
+                # Check for successful startup
+                if "running on http" in output.lower():
+                    break
+        
+        # Terminate the process
+        process.terminate()
+        process.wait(timeout=10)
+        
+        if scheduler_found and verification_found:
+            print("✅ APScheduler is visible during application startup")
+            return True
+        else:
+            print("❌ APScheduler messages not found in startup logs")
+            return False
+            
+    except Exception as e:
+        print(f"❌ Error testing app startup: {e}")
+        return False
+
+def main():
+    """Main integration test function."""
+    print("🔗 Testing APScheduler integration with Flask application...")
+    print("=" * 60)
+    
+    success = test_app_startup_with_scheduler()
+    
+    print("\n" + "=" * 60)
+    if success:
+        print("🎉 Integration test passed! APScheduler is working in the Flask app.")
+    else:
+        print("⚠️ Integration test failed. APScheduler may not be properly configured.")
+    
+    return success
+
+if __name__ == "__main__":
+    success = main()
+    sys.exit(0 if success else 1)

test_scheduler_visibility.py

@@ -0,0 +1,186 @@
+#!/usr/bin/env python3
+"""
+Test script for APScheduler visibility and functionality.
+This script tests whether APScheduler is working and properly configured for logging.
+"""
+
+import sys
+import os
+import logging
+from pathlib import Path
+from datetime import datetime
+
+# Add the backend directory to the Python path
+backend_dir = Path(__file__).parent / "backend"
+sys.path.insert(0, str(backend_dir))
+
+def setup_logging():
+    """Setup logging for the test script."""
+    logging.basicConfig(
+        level=logging.DEBUG,
+        format='%(asctime)s - %(name)s - %(levelname)s - %(message)s'
+    )
+    # Configure APScheduler logger specifically
+    logging.getLogger('apscheduler').setLevel(logging.DEBUG)
+    print("Logging configured for APScheduler")
+
+def test_apscheduler_import():
+    """Test that APScheduler can be imported."""
+    try:
+        from backend.scheduler.apscheduler_service import APSchedulerService
+        print("SUCCESS: APSchedulerService imported successfully")
+        return True
+    except Exception as e:
+        print(f"ERROR: Failed to import APSchedulerService: {e}")
+        return False
+
+def test_scheduler_initialization():
+    """Test APScheduler initialization with mock app."""
+    try:
+        from backend.scheduler.apscheduler_service import APSchedulerService
+        
+        # Create a mock app object
+        class MockApp:
+            def __init__(self):
+                self.config = {
+                    'SUPABASE_URL': 'https://test.supabase.co',
+                    'SUPABASE_KEY': 'test_key',
+                    'SCHEDULER_ENABLED': True
+                }
+        
+        # Initialize the scheduler service
+        app = MockApp()
+        scheduler_service = APSchedulerService()
+        
+        # Mock the Supabase client initialization
+        class MockSupabaseClient:
+            def table(self, table_name):
+                return self
+                
+            def select(self, columns):
+                return self
+                
+            def execute(self):
+                # Return empty schedule data for testing
+                return type('obj', (object,), {'data': []})()
+        
+        scheduler_service.supabase_client = MockSupabaseClient()
+        
+        # Test initialization
+        scheduler_service.init_app(app)
+        
+        if scheduler_service.scheduler is not None:
+            print("SUCCESS: APScheduler initialized successfully")
+            print(f"INFO: Current jobs: {len(scheduler_service.scheduler.get_jobs())}")
+            return True
+        else:
+            print("ERROR: APScheduler initialization failed")
+            return False
+            
+    except Exception as e:
+        print(f"ERROR: Error testing APScheduler initialization: {e}")
+        import traceback
+        traceback.print_exc()
+        return False
+
+def test_schedule_loading():
+    """Test the schedule loading functionality."""
+    try:
+        from backend.scheduler.apscheduler_service import APSchedulerService
+        
+        # Create scheduler service
+        scheduler_service = APSchedulerService()
+        
+        # Mock the Supabase client
+        class MockSupabaseClient:
+            def table(self, table_name):
+                return self
+                
+            def select(self, columns):
+                return self
+                
+            def execute(self):
+                # Return mock schedule data
+                mock_data = [
+                    {
+                        'id': 'test_schedule_1',
+                        'schedule_time': 'Monday 09:00',
+                        'adjusted_time': 'Monday 08:55',
+                        'Social_network': {
+                            'id_utilisateur': 'test_user_1',
+                            'token': 'test_token',
+                            'sub': 'test_sub'
+                        }
+                    }
+                ]
+                return type('obj', (object,), {'data': mock_data})()
+        
+        scheduler_service.supabase_client = MockSupabaseClient()
+        
+        # Test schedule loading
+        scheduler_service.load_schedules()
+        
+        if scheduler_service.scheduler is not None:
+            jobs = scheduler_service.scheduler.get_jobs()
+            print(f"SUCCESS: Schedule loading test completed")
+            print(f"INFO: Total jobs: {len(jobs)}")
+            
+            # Check for specific job types
+            loader_jobs = [job for job in jobs if job.id == 'load_schedules']
+            content_jobs = [job for job in jobs if job.id.startswith('gen_')]
+            publish_jobs = [job for job in jobs if job.id.startswith('pub_')]
+            
+            print(f"INFO: Loader jobs: {len(loader_jobs)}")
+            print(f"INFO: Content generation jobs: {len(content_jobs)}")
+            print(f"INFO: Publishing jobs: {len(publish_jobs)}")
+            
+            return len(jobs) > 0
+        else:
+            print("ERROR: Scheduler not initialized for schedule loading test")
+            return False
+            
+    except Exception as e:
+        print(f"ERROR: Error testing schedule loading: {e}")
+        import traceback
+        traceback.print_exc()
+        return False
+
+def main():
+    """Main test function."""
+    print("Testing APScheduler visibility and functionality...")
+    print("=" * 60)
+    
+    setup_logging()
+    
+    tests = [
+        ("APScheduler Import", test_apscheduler_import),
+        ("Scheduler Initialization", test_scheduler_initialization),
+        ("Schedule Loading", test_schedule_loading),
+    ]
+    
+    passed = 0
+    total = len(tests)
+    
+    for test_name, test_func in tests:
+        print(f"\nRunning test: {test_name}")
+        print("-" * 40)
+        
+        if test_func():
+            passed += 1
+            print(f"SUCCESS: {test_name} PASSED")
+        else:
+            print(f"FAILED: {test_name} FAILED")
+    
+    print("\n" + "=" * 60)
+    print(f"Test Results: {passed}/{total} tests passed")
+    
+    if passed == total:
+        print("SUCCESS: All tests passed! APScheduler is working correctly.")
+        return True
+    else:
+        print("WARNING: Some tests failed. Please check the error messages above.")
+        return False
+
+if __name__ == "__main__":
+    success = main()
+    sys.exit(0 if success else 1)