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-07 UTC."],[[["The page details the `FailedPreconditionException` class, which is thrown when an operation fails due to the system not being in the correct state for execution, such as attempting to delete a non-empty directory."],["This exception class extends `ApiException` and includes inherited members like `getDomain()`, `getErrorDetails()`, `getMetadata()`, `getReason()`, `getStatusCode()`, and `isRetryable()`."],["The page offers documentation on the `FailedPreconditionException` class across a range of versions, from the latest (2.63.1) down to 2.7.1."],["There are three constructors available for `FailedPreconditionException`, with variations in parameters including `message`, `cause`, `statusCode`, `retryable`, and `errorDetails`."]]],[]]