# BLOB_BAK_CRASH: File backup worker crashed mid-run

- Module: BLOB. Blob storage replication R2 → Hetzner (scout sync-blob-backup)
- Severity: Critical
- Impact: No impact. Bookkeeping only. Nobody is affected.
- Retry: Automatic. The platform retries or self-heals on its own.
- Reference: https://docs.bizkithub.com/en/system-codes/BLOB_BAK_CRASH

## What happened

An unexpected error (such as a database timeout, a storage provider outage or running out of memory on a large file) stopped the file backup run early. Files already marked as backed up are safe, and the reported count is accurate. The next run continues from where this one stopped; repeated failures mean the underlying resource is down.

## Likely causes

- The file backup worker hit an unexpected error such as a database timeout or storage outage.
- A very large file exhausted the worker's resources.

## How to resolve

1. No customer action is needed; files already backed up are safe and the worker resumes on its next run.
2. Persistent repeats indicate a platform-side outage that BizKitHub operations will handle; contact support@bizkithub.com if file access is affected.

## Related codes

- BLOB_BAK_PUT_F: Backup S3 PUT failed (R2 → Hetzner mirror)
- BLOB_BAK_NOENV: Blob backup worker ran without backup credentials