diff --git a/docs/concepts/crds/backupconfiguration/index.md b/docs/concepts/crds/backupconfiguration/index.md
index e9319c6e..32f799ca 100644
--- a/docs/concepts/crds/backupconfiguration/index.md
+++ b/docs/concepts/crds/backupconfiguration/index.md
@@ -186,7 +186,7 @@ Stash does not support providing days (`d`) in the `timeOut` field. Use the equi
   - `Always`: The hook will be executed after the backup process no matter the backup has failed or succeeded. This is the default behavior.
   - `OnSuccess`: The hook will be executed after the backup process only if the backup has succeeded.
   - `OnFailure`: The hook will be executed after the backup process only if the backup has failed.
-
+  - `OnFinalRetryFailure`: The hook will be executed after the backup process only if the backup has failed with no more retry attempts left.
 For more details on how hooks work in Stash and how to configure different types of hook, please visit [here](/docs/guides/hooks/overview/index.md).
 
 #### spec.runtimeSettings
diff --git a/docs/guides/hooks/overview/index.md b/docs/guides/hooks/overview/index.md
index 1d067f2d..146055ae 100644
--- a/docs/guides/hooks/overview/index.md
+++ b/docs/guides/hooks/overview/index.md
@@ -89,6 +89,7 @@ If the backup or restore process fails then the respective `postBackup` or `post
 - `Always`: The hook will be executed after the backup/restore process no matter the backup/restore has failed or succeeded. This is the default behavior.
 - `OnSuccess`: The hook will be executed after the backup/restore process only if the backup/restore has succeeded.
 - `OnFailure`: The hook will be executed after the backup/restore process only if the backup/restore has failed.
+- `OnFinalRetryFailure`: The hook will be executed after the backup process only if the backup has failed with no more retry attempts left.
 
 If the `postBackup` or `postRestore` hook fails, the respective BackupSession or RestoreSession will be marked as `Failed`.