Bug Fixing and Incident Resolution
Your application crashes, a bug blocks your users, an incident impacts your business: we intervene rapidly to diagnose, fix, and stabilize.
What is corrective maintenance ?
Corrective maintenance consists of identifying and resolving anomalies that impact the functioning of your web application : functional bugs, technical errors, regressions following an update, or production incidents.
Unlike preventive maintenance which anticipates problems, corrective maintenance intervenes after a malfunction has been detected. The goal: to restore the service as quickly as possible, then understand the root cause to prevent recurrence.
When do you need corrective maintenance ?
Your application displays 500 errors in production
A bug prevents your users from completing a key action
A regression appeared after a deployment
Data is corrupted or missing
Performance has suddenly degraded
A third-party component (API, service) is no longer responding
What corrective maintenance covers
Functional Bugs
Unexpected behaviors, incorrect calculations, broken user journeys, forms that no longer submit, broken features after deployment.
Production Incidents
500 errors, timeouts, unavailable services, unmanaged load spikes, application crashes.
Data Problems
Corruption, inconsistencies, duplicates, data loss, migration or synchronization errors.
Failing Integrations
Third-party APIs failing, webhooks no longer responding, broken synchronizations with your tools (CRM, ERP).
From reporting to resolution in 4 steps
Reporting & Qualification
You report the incident via your preferred channel (Jira, GitLab, email, Slack). We qualify the priority (P1/P2/P3) and confirm that we are taking charge.
P1 : response < 1hDiagnosis & Root Cause
Log analysis, bug reproduction, identification of the cause. We provide you with a clear diagnosis and an estimated time for the fix.
Diagnosis shared within 2h for P1Fix & Deployment
Fix developed, tested, reviewed, then deployed to production. Rollback possible at any time in case of regression.
Hotfix deployable within 4h for P1Post-mortem & Prevention
Documented incident report : cause, impact, resolution, and preventive measures to avoid recurrence.
Report within 48hOur Service Level Agreement Commitments
Contractually guaranteed response and resolution times, adapted to the criticality of the incident.
How we resolved a production incident
Problem
B2B SaaS platform, users cannot export their reports since the Friday evening update. 200 clients impacted, growing loss of trust.
Diagnosis (45 min)
Sentry log analysis : the PDF library update introduced an incompatibility with the data format. The bug was not covered by existing tests.
Resolution & Prevention (2h30)
Deployment of a compatibility patch via the CI/CD pipeline. Long-term securing via a client post-mortem, addition of tests (regression and E2E), and implementation of an automated smoke test.
Results
Questions about corrective maintenance
Do you intervene outside of office hours ?
Yes, for P1 (critical) incidents, our on-call team is available in the evenings and on weekends. The exact terms are defined in the maintenance contract.
How do I report an incident ?
Via your usual channel : Jira or GitLab ticket, dedicated email, Slack, or phone for emergencies. We adapt to your tools, no need to change your habits.
What happens if the bug comes from a third-party component ?
We diagnose and propose an immediate workaround, then we contact the publisher or look for an alternative. The resolution time for the workaround remains covered by our SLA.
Is corrective maintenance included in an AMS (Application Maintenance Support) contract?
Yes, it is the basic building block of any application maintenance contract. It can be supplemented by evolutive maintenance, preventive maintenance, and support/monitoring.
