Skip to main content

Reports and Bulk Operations Troubleshooting

Symptoms

A report tab is unavailable/current-state values differ, or import/export API operation fails.

Scope

Recruitment report UI/endpoints and native CSV APIs. There is no Recruitment bulk UI.

Cause

Likely causes

  • One report endpoint failed while others succeeded.
  • Report is current-state, not historical analytics.
  • Bulk input validation failed.
  • Authorization, limits, and sensitive-data export governance require confirmation.

Safe diagnostic steps

  1. Identify report tab or bulk API category.
  2. For reports, compare source/current-state read and retry once through UI.
  3. For bulk API, review validation summary using synthetic non-sensitive data.
  4. Do not export or attach candidate/offer data to support evidence.

Resolution

Safe resolution

Correct valid synthetic input or restore the failing report dependency. Escalate governance/limits; do not manipulate database rows.

Validation

Confirm report availability/current-state semantics or accepted validation outcome for an approved synthetic bulk scenario.

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 report/query to Recruitment, UI to frontend, bulk governance to product/security/privacy, and routing to Gateway.

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsx
  • microservices/src/recruitment-service/Api/RecruitmentEndpoints.cs
  • microservices/src/recruitment-service/Application/Queries/RecruitmentQueries.cs

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