# BLOB_BAK_NOENV: Blob backup worker ran without backup credentials

- Module: BLOB. Blob storage replication R2 → Hetzner (scout sync-blob-backup)
- Severity: Warning
- Impact: No impact. Bookkeeping only. Nobody is affected.
- Retry: Not retryable. Retrying will not help until the cause is fixed.
- Reference: https://docs.bizkithub.com/en/system-codes/BLOB_BAK_NOENV

## What happened

Scout invoked `sync-blob-backup` but one or more of `BACKUP_S3_ACCESS_KEY`, `BACKUP_S3_SECRET_ACCESS_KEY`, or `BACKUP_S3_ENDPOINT` is missing. The worker exits cleanly as a no-op and logs this code once per 30 min. Populate the VPS `.env` and restart the timer.

## Likely causes

- The file backup worker ran without its backup storage configuration.

## How to resolve

1. This is a platform configuration issue handled by BizKitHub operations; no organisation action is needed.
2. Backups resume once the configuration is restored.

## Related codes

- BLOB_BAK_CRASH: File backup worker crashed mid-run
- BLOB_BAK_PUT_F: Backup S3 PUT failed (R2 → Hetzner mirror)