FolioIntent help

Maintenance and data care

FolioIntent is local-first. You remain responsible for long-term copies and the health of destinations you operate.

Before updating or migrating

• Finish or inspect pending and ambiguous actions in Runs. Use Retry only for Ready to retry, Check Provider for existing provider-bound work, and the reconnect flow only for Authentication required. Reconnect and resubmission are separate actions.
• Export documents and results you must keep to Files or another backed-up destination.
• Keep the existing app installed until the updated version has opened and your library is visible.
• Record destination settings separately without copying secrets into notes or email.

Backups and storage

Result leases and the visible library are not a backup policy. Save important outputs to storage you control and verify that its own backup or sync completed. iOS may remove an app's local container when you delete the app.

Rotate destination credentials

1. Check for unresolved delivery actions before revoking the old credential.
2. Create a least-privilege replacement at the destination.
3. Update FolioIntent and test with a non-sensitive sample.
4. Confirm the destination received the sample, then revoke the old credential.

Local and remote availability

FolioIntent does not run a hosted document-processing service, so there is no FolioIntent upload-service status to monitor. Apple services govern App Store purchases and installation. Your Files provider, Photos library, Paperless server, WebDAV server, or S3-compatible service governs its own availability.

When recovery is required

Preserve the app and its local data, avoid repeated retries, and contact [email protected] with sanitized version and error details. Do not uninstall the app or delete source files while an uncertain delivery is being investigated.