IRC Log Rollback System

Overview

The rollback system provides a safety mechanism to undo accidental production imports. If logfiles are imported to production by mistake, you can now easily remove them without manual database surgery.

Key Features

1. Approval Tracking

• When a job is approved for production, the system records:
  • Who approved it (approved_by_user_id)
  • When it was approved (approved_at)
  • The approval info is also copied to the batch record for audit trail

2. Batch Linking

• Each approved job maintains a reference to its production batch (production_batch_id)
• Batches maintain a complete audit trail showing:
  • When they were approved
  • Who approved them
  • Any rollbacks that occurred

3. Rollback Process

The rollback system provides a multi-step process:

1. Confirm - Review job details and provide a rollback reason
2. Execute - Permanently delete all events from production matching this batch
3. Audit - Track all rollbacks in the audit history

4. Audit Trail

All rollback actions are permanently recorded:

• Who initiated the rollback
• When it occurred
• The reason for the rollback
• How many events were deleted

Using the Rollback Feature

Step 1: Identify Problem Job

Go to Admin → IRC Memory Lane and find the job that needs to be rolled back.

Step 2: Click Rollback

From the job detail page, if the job is completed (status = "done"), you'll see a "🔄 Rollback from Production" button.

Step 3: Confirm Rollback

• Review the job and batch details
• Provide a detailed reason for the rollback (required, min 10 characters)
• Check the confirmation checkbox
• Click "Execute Rollback"

Step 4: Verify

The page will show:

• How many events were deleted
• Confirmation that the rollback was successful
• The rollback is now recorded in the audit trail

Viewing Rollback History

To see all past rollbacks:

1. Go to Admin → IRC Memory Lane
2. Click "Rollback History" button
3. View the complete audit trail of all rollbacks

Each entry shows:

• Batch ID
• Source file
• When it was rolled back
• Who rolled it back
• The reason provided

Database Changes

Two new migrations add rollback tracking:

Migration: 2026_03_01_000000_add_rollback_tracking_to_batches.php

Adds columns to both import_batches and irclog_import_jobs tables:

• approved_by_user_id - User who approved the job
• approved_at - Timestamp of approval
• is_rolled_back - Whether this has been rolled back
• rolled_back_at - When the rollback occurred
• rolled_back_by_user_id - Who initiated the rollback
• rollback_reason - Why it was rolled back

Migration: 2026_03_01_000001_add_irclog_permissions.php

Adds two new permissions:

• irclog.manage - Can manage IRC logs
• irclog.rollback - Can rollback production imports

API Endpoints

GET /admin/irclog/{jobId}/rollback

Show confirmation page for rollback

POST /admin/irclog/{jobId}/rollback

Execute the rollback

Request body:

{
  "reason": "Accidental import of test data"
}

GET /admin/irclog/rollback/history

View rollback audit trail

GET /admin/irclog/api/rollback/{jobId}

Get rollback info for a job (API response)

Response:

{
  "rolled_back": true,
  "rolled_back_at": "2026-03-01T15:30:00Z",
  "rolled_back_by": "Thomas Tornevall",
  "reason": "Accidental import"
}

Service: ImportRollbackService

The App\Services\IrcLog\ImportRollbackService class handles all rollback logic:

// Rollback a job
$service = app(ImportRollbackService::class);
$result = $service->rollbackJob($jobId, $user, 'Reason...');

// Check if successful
if ($result['success']) {
    echo "Rolled back! " . $result['message'];
    echo "Deleted " . $result['stats']['events_deleted'] . " events";
}

// Get rollback info
$info = $service->getRollbackInfo($jobId);
if ($info) {
    echo "Rolled back by: " . $info['rolled_back_by'];
}

// Get all rollbacks
$history = $service->getRolledBackBatches(100);

Important Notes

⚠️ Permanent Deletion: Rollback permanently deletes events from production. Make sure you have backups before proceeding.

⚠️ Referential Integrity: If other systems reference the deleted events, they may break. Use sparingly.

✓ Audit Trail: All rollbacks are traceable and cannot be undone. They are recorded in the database permanently.

✓ Permission Control: Only users with irclog.manage permission can rollback.

Example Scenario

1. You upload a 10,000 event log file
2. Dry-run shows 10,000 events to import
3. You approve and merge to production
4. An hour later, you realize it was a test file that shouldn't be in production
5. Go to IRC Log Admin → find the job → click "Rollback from Production"
6. Provide reason: "Test data accidentally imported"
7. Confirm by checking the checkbox
8. Click "Execute Rollback" - all 10,000 events are deleted
9. Go to "Rollback History" to verify it's recorded

Troubleshooting

"No production batch found for this job"

• This job was never merged to production, so there's nothing to rollback
• Check that the job status is "done"

"This job has already been rolled back"

• The job was previously rolled back
• Check the rollback history for details

Rollback seems to hang or timeout

• Very large batches may take time
• Check server logs for detailed error messages
• Contact support if it continues

Future Enhancements

Potential improvements to consider:

• Soft-delete instead of permanent delete
• Rollback preview (show what would be deleted)
• Batch rollback (multiple jobs at once)
• Rollback to a specific time point
• Automatic rollback on import errors