# [ERROR] [my_lifecycle_node]: Failed to configure: required parameter 'my_param' not set

- **ID:** `ros2/lifecycle-node-configure-failure-no-parameters`
- **Domain:** ros2
- **Category:** config_error
- **Verification:** ai_generated
- **Fix Rate:** 90%

## Root Cause

A lifecycle node's on_configure callback requires a parameter that is not provided in the node's parameter list, causing the transition to fail.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| ROS2 Foxy | active | — | — |
| ROS2 Galactic | active | — | — |
| ROS2 Humble | active | — | — |
| rclcpp 16.x | active | — | — |

## Workarounds

1. **Provide the missing parameter via a YAML file or command line: 'ros2 run my_package my_lifecycle_node --ros-args -p my_param:=value'** (95% success)
   ```
   Provide the missing parameter via a YAML file or command line: 'ros2 run my_package my_lifecycle_node --ros-args -p my_param:=value'
   ```
2. **Modify the node's on_configure to use a default value if the parameter is not set: if (!this->get_parameter('my_param', my_param_)) { my_param_ = default_value; }** (85% success)
   ```
   Modify the node's on_configure to use a default value if the parameter is not set: if (!this->get_parameter('my_param', my_param_)) { my_param_ = default_value; }
   ```

## Dead Ends

- **** — The parameter may still not be set if the user doesn't provide a value; the error occurs only if the parameter is explicitly required without a default. (50% fail)
- **** — Parameters must be declared before configure; reordering doesn't fix missing parameter values. (90% fail)
- **** — The lifecycle state machine prevents activation without successful configuration. (100% fail)