Operations6 min
Documents and logs
Manage local files, inspect provenance, and diagnose common failures.
Document library
- Search by filename or source URL.
- The download icon serves one verified local file through the backend when only a specific document is needed.
- Download all creates one ZIP containing every available document plus a manifest.json file with source and integrity metadata. When search is active, Download results includes only matching documents.
- The archive is assembled on temporary server disk instead of being loaded into RAM. Keep free-tier exports small; large production libraries should export from durable object storage.
- Rename changes both the local filename and the metadata record; the extension cannot be changed.
- Delete removes one local file and its metadata record after an explicit confirmation.
- Clear library removes every document record from the application screen but never deletes files from PC folders. A later crawl may index those files again.
- A missing-file warning means metadata exists but the file was moved or deleted outside the application; delete the stale record to clean it up.
Runtime logs
Crawler, download, and error logs are separate so operational events are easier to filter. The Logs page refreshes automatically, supports text filtering, and can truncate the current log set after confirmation.
Common errors
- ERR_INTERNET_DISCONNECTED: the machine or target connection was unavailable during navigation.
- Timeout: the target did not respond within the configured request limit.
- robots.txt denied: publisher policy blocked the requested page.
- Local file no longer exists: the document was changed outside UDC Pro.
- Backend disconnected: the frontend cannot reach NEXT_PUBLIC_API_URL; check the backend terminal and port.