Skip to main content

🔐 Managing Access Loss (EPERM)

Written by Nicolas Movio

What is this?

When syncing a network disk source, Outmind accesses files using a service account.

In some cases, this account may lose access to certain files or folders (EPERM error), for example due to:

  • permission changes on the source system

  • file ownership changes

  • service account misconfiguration

What does the "Protect against access loss" option do?

This option, available only for network drive sources, determines how Outmind behaves when a file becomes inaccessible.

Option enabled (recommended)

  • Files remain visible in Outmind

  • They are not removed from the index

  • Their content may become outdated if changes occur

👉 Goal: prevent unintended large-scale deletions

Option disabled

  • Inaccessible files are removed from the index

  • They are no longer visible in Outmind

👉 Risk: if the service account is misconfigured or loses permissions, this can lead to massive deindexing

Why is this option recommended?

In most cases, access loss is:

  • temporary

  • or caused by a configuration issue

Keeping files in the index helps:

  • avoid sudden data loss

  • give time to fix permission issues

When should you disable this option?

Possible cases:

  • you need to strictly reflect current access permissions

  • strong compliance or security requirements

  • a controlled environment where permissions are stable and reliable

Best practices

  • Verify service account permissions before syncing

  • Monitor permission changes on the source system

  • Only disable this option if the behavior is fully understood

Did this answer your question?