Exception thrown when the operation was rejected because the system is not in a state required
for the operation's execution. For example, directory to be deleted may be non-empty, an rmdir
operation is applied to a non-directory, etc.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-15 UTC."],[[["The page details the `FailedPreconditionException` class, which is thrown when an operation fails due to the system not being in the correct state, such as attempting to delete a non-empty directory."],["The `FailedPreconditionException` class extends `ApiException` and includes inherited members like `getDomain()`, `getReason()`, and `isRetryable()`, among others, for more comprehensive error handling."],["This page has an exhaustive list of versions of `FailedPreconditionException` ranging from version 2.63.1 down to version 2.7.1."],["The class offers three constructors that allow for specifying the error message, cause, status code, retryable status, and optionally, error details, providing flexibility in error reporting."]]],[]]