overleaf/overleaf · error

Some files could not be processed, see logs in ${OUTPUT_FILE

Error message

Some files could not be processed, see logs in ${OUTPUT_FILE} and try again

What it means

Exit-time summary in the back-fill script: STATS.filesFailed > 0, meaning at least one file could not be hashed/migrated during the run. The script bumps its exit code so automation can detect the incomplete pass and points the operator at the detailed failure log in OUTPUT_FILE.

Source

Thrown at services/history-v1/storage/scripts/back_fill_file_hash.mjs:1479

if (DISPLAY_REPORT) {
  await cleanupBufferDir()
  console.warn('Displaying report...')
  await displayReport()
  process.exit(0)
}

try {
  try {
    await main()
  } finally {
    printStats(true)
    await cleanupBufferDir()
  }

  let code = 0
  if (STATS.filesFailed > 0) {
    console.warn(
      `Some files could not be processed, see logs in ${OUTPUT_FILE} and try again`
    )
    code++
  }
  if (STATS.fileHardDeleted > 0) {
    console.warn(
      'Some hashes could not be updated as the files were hard-deleted, this should not happen'
    )
    code++
  }
  if (STATS.projectHardDeleted > 0) {
    console.warn(
      'Some hashes could not be updated as the project was hard-deleted, this should not happen'
    )
    code++
  }
  console.warn('-'.repeat(79))
  if (code === 0) {

View on GitHub (pinned to 28ad3b03b7)

Solutions

1. Review OUTPUT_FILE for the per-file failure reasons
2. Fix the underlying causes (unreadable files, transient store errors) and re-run; the script is resumable
3. Monitor the exit code in automation so failed back-fills are not silently dropped

When it happens

Trigger: Thrown at services/history-v1/storage/scripts/back_fill_file_hash.mjs:1479 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of overleaf/overleaf@28ad3b03b7 (2026-09-03). Data as JSON: /api/errors/bee2fd023f489f4f. Report an issue: GitHub.