BizKitHub
BLOB_BAK_CRASH

File backup worker crashed mid-run

CriticalBLOBRetry: automatic
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. 1

    No customer action is needed; files already backed up are safe and the worker resumes on its next run.

  2. 2

    Persistent repeats indicate a platform-side outage that BizKitHub operations will handle; contact [email protected] if file access is affected.

Where you will see it

The code tags entries in the admin Log viewer, where you can filter by it and open individual occurrences. Codes logged as error or critical can also trigger a technical notification e-mail with the code in the subject:

Notification subject
[BLOB_BAK_CRASH] [blob] …