Glossary · Fault behavior and system states
Partial failure
In systems engineering, a partial failure is a condition in which only part of an integrated system or transaction fails while other parts continue to operate.
- Integrated systems
- Functional safety
In one sentence
A partial failure leaves part of an integrated system running while another part has failed, which makes it hard to detect and recover from.
Example
A palletizing robot completes its motion, but the confirmation to the warehouse system is lost; the line runs on while inventory data and physical stock disagree.
How it applies
- Integrated systems: Identify which parts of an integrated system can fail independently and what state the rest is left in. Transactions that span several systems need rules for completing or undoing half-finished steps.
- Functional safety: Partial failures can create interaction hazards: one machine keeps feeding material while the next one has stopped. The fault reaction must consider the whole line, not only the failed element.
- Recovery: Define recovery behavior that resynchronizes states before restart. Idempotency makes it safe to repeat interrupted operations.
- Technical documentation: Troubleshooting instructions should cover inconsistent states, not only complete failures.
Partial failure vs. total failure
A total failure is usually obvious and stops everything. A partial failure lets the system look operational while its parts no longer agree, so it must be detected actively, for example by timeouts, acknowledgments and consistency checks.