Skip to main content

Performance Workflow Operations

Summary​

Workflow delegation is feature-selected. When disabled, a null client preserves local review behavior. When enabled, self submission starts an approval workflow, persists linkage separately, and later accepts a terminal callback subject to state and optional remote verification.

Start failure policy differs by environment behavior in source and must be reviewed by owners without exposing fallback details. HTTP availability, callback acceptance, and broker delivery are separate concerns.

Safety and confirmation boundary​

No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.

Source References​

  • microservices/src/performance-service/Application/WorkflowIntegration.cs
  • microservices/src/performance-service/Infrastructure/WorkflowServiceClient.cs
  • microservices/src/performance-service/Application/Commands/AppraisalCommands.cs

See Also​

Keywords​

  • Performance operations
  • Safe support guidance

Revision Information​

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