Onping enables teams to orchestrate manual steps inside serverless and container workflows, but certain actions still need explicit human judgment. On the Onping automation platform, you can create a manual parameter that pauses execution and waits for operator input before continuing the deployment pipeline.
This approach combines event-driven automation with controlled human intervention, reducing risk while preserving speed. The following sections outline how to design, configure, and troubleshoot manual parameters for high-stakes workflows.
| Parameter Type | Trigger Condition | Default Value | Override Allowed |
|---|---|---|---|
| Manual Approval | Pre-production stage | Pending | No |
| Environment Selector | Rollout phase | Staging | Yes |
| Retry Threshold | Failed health check | 3 | Yes |
| Approval Timeout | No response | 60 minutes | Yes |
Defining Manual Parameter Logic in Workflows
At the core of controlled automation is a manual parameter that waits for an authorized user to provide input. Onping lets you define the parameter schema, validation rules, and runtime visibility directly in the pipeline definition.
You specify the parameter type, acceptable ranges, and conditional visibility so that operators see only the fields relevant to their context. This design keeps the execution graph predictable while giving humans the necessary levers at the right moment.
Configuring Parameter Schema and Validation
Each manual parameter requires a clear schema that describes its data type, constraints, and default behavior. Onping provides a declarative schema format where you can enforce formats, enumerated values, and mandatory flags.
Validation runs before the pause, rejecting malformed input and attaching inline error messages to the operator interface. By aligning schema definitions with your existing configuration standards, you reduce ambiguity and prevent runtime exceptions downstream.
Schema Definition Fields
- Parameter name and description for operator clarity
- Data type, such as string, integer, or boolean
- Allowed values, ranges, and pattern constraints
- Conditional visibility based on environment or tag
Integrating Manual Steps into CI/CD Pipelines
Placing a manual parameter in the right stage of your CI/CD pipeline balances speed with safety. Common use cases include pre-production approval, production promotion gates, and emergency rollback authorization.
Onping connects these manual steps to your existing notification channels, so approvers receive timely alerts with context. The platform records who approved, when, and with which parameter set, creating a complete audit trail for compliance.
Monitoring and Timeout Configuration
Even well-designed manual steps can stall if approvers are unavailable, which is why timeout configuration is essential. You can set per-parameter timeouts, escalation rules, and fallback behaviors when human input is missing.
Monitoring dashboards highlight pending manual interventions, allowing team leads to reassign or expedite decisions. With configurable alerts and timeout policies, you keep automation flowing without sacrificing necessary oversight.
Operational Best Practices for Manual Parameters
Using manual parameters effectively requires discipline in design, communication, and observability across your automation landscape.
- Document the purpose and expected input for every manual parameter in the pipeline README
- Define clear timeout and escalation policies aligned with your incident response processes
- Use naming conventions that distinguish manual parameters from automated variables
- Test manual steps in a staging environment to validate notifications and fallback paths
- Review parameter usage periodically to remove obsolete pauses and simplify workflows
FAQ
Reader questions
How do I reference a manual parameter later in the workflow?
You reference a manual parameter by its defined variable name, which becomes available to downstream steps once the operator provides a value. Onping injects the value into runtime context so subsequent tasks, tests, and deployments can use it seamlessly.
Can I restrict manual approval to specific teams or roles?
Yes, you can scope manual approval steps to specific teams or roles using access control rules defined in the pipeline. Onping evaluates these permissions at runtime, ensuring only authorized users can submit input during the pause.
What happens to the workflow if the approval timeout expires?
When the approval timeout expires, Onping follows the configured fallback behavior, which may include automatic cancellation, retry notification, or escalation to a backup approver. The event is logged with timestamps and reasons to support incident review.
How do I update a manual parameter value after the workflow has started?
Manual parameter values are locked after submission to preserve execution integrity, but you can initiate a new run or create a parameterized restart when business needs change. Versioned pipeline definitions help you track how parameter expectations evolve over time.