Skip to main content

Recruitment Database and Migration Troubleshooting

Symptoms​

Startup migration fails, schema/read operations fail, or data appears inconsistent.

Scope​

Recruitment database configuration, EF migrations, tenant filters, native/compatibility shared storage, and production out-of-band migration.

Cause​

Likely causes​

  • Database category is unavailable/misconfigured.
  • Expected migration was not approved/applied.
  • Development auto-migration assumption was used in Production.
  • Tenant or compatibility mapping creates an apparent mismatch.

Safe diagnostic steps​

  1. Confirm environment category and approved migration record.
  2. Check process/startup errors and migration identifier through sanitized evidence.
  3. Use supported reads to distinguish schema, tenant, and mapping issues.
  4. Stop before any direct database modification.

Resolution​

Safe resolution​

Database and service owners must apply the approved migration/recovery process. Documentation provides no direct-edit procedure.

Validation​

Verify process health, schema-compatible supported reads, tenant isolation, and representative compatibility/native read consistency.

Evidence to collect​

Collect the time window, environment category, affected operation, expected/actual status category, safe record reference, correlation reference where available, dependency/error category, and recent approved change. Exclude personal data, resumes/documents, interview notes, tokens, offer/compensation values, credentials, bank/KYC data, secrets, and configuration values.

Escalation​

Escalate to database owner, Recruitment owner, DevOps/SRE, and architecture for shared-storage/cutover issues.

Source References​

  • microservices/src/recruitment-service/Program.cs
  • microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
  • microservices/src/recruitment-service/Infrastructure/Migrations

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly