Database and Migration
Summary
Service startup or Attendance persistence fails with a database/migration category.
Audience
Employees or administrators affected by the scenario, first-line support, QA, service owners, and operations.
Symptoms
- Service startup or Attendance persistence fails with a database/migration category.
Scope
Attendance Service persistence and startup migration behavior.
Likely causes
Database unavailable, incompatible migration state, insufficient approved service access, or startup migration suppression/ownership mismatch.
Cause
The confirmed cause categories are listed under Likely causes above; determine the applicable category from sanitized evidence before taking action.
Safe diagnostic steps
- Check process/startup logs, health, migration evidence, database availability through approved monitoring, and correlation/timestamp. Do not expose connection details.
- Preserve tenant isolation and redact personal or security-sensitive data.
- Do not use direct database changes, authorization bypasses, or ad hoc broker operations.
Safe resolution
Restore dependency access or execute the organization-approved migration/rollback runbook under database/service ownership. Do not edit schema/data manually.
Resolution
Apply only the Safe resolution described above and remain within the documented ownership boundary.
Validation
Restart only under approved procedure; verify health and a safe tenant-scoped read.
Evidence to collect
Deployment version, migration identifier/state, timestamp, sanitized error category, service/database signals.
Escalation
Database owner and Attendance service owner; DevOps/SRE for platform availability.
Related docs
Related Articles
Source References
microservices/src/attendance-service/Program.csmicroservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
See Also
Keywords
- Attendance
- Troubleshooting
- Database and Migration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly