Batch Processing
Folder actions share selection and progress controls, but retain different output and overwrite behavior. The default concurrency is one. Start with a dedicated test folder, inspect the selected scope and destinations, then expand the batch.
Overview
Use the sidebar's folder action or the corresponding file-explorer menu. Supported folder tasks include add-links, concept extraction, title generation, translation, original-text extraction, Mermaid repair and formula repair. There is no generic folder-research action; title generation can optionally include research.
A batch is not a transaction across the whole folder. Successfully written outputs remain if another file fails or the operation is cancelled.
How It Works
Batch Execution Model
- Select the task and folder. Confirm that the folder contains only files you intend to process.
- The task collects eligible files, applies its extension and selection rules, and excludes any task-specific output files.
- It uses the task's configured provider/model and reports progress, failures and destinations.
- On completion or cancellation, review the report and output files before retrying.
Default folder scope includes subfolders for add-links, concept extraction, title generation, original-text extraction, Mermaid repair and formula repair. Folder translation defaults to direct children only. Advanced file-selection profiles can override scope and filtering when both developer mode and advanced file selection are enabled. Check the actual profile rather than assuming every task recurses identically.
Overwrite Behavior
| Task | What to inspect before a repeat run |
|---|---|
| Add links | Separate processed outputs by default; check custom suffix, output folder and move-original settings |
| Concept extraction | Existing concept notes can receive backlinks when enabled; duplicate detection is separate |
| Title generation | Generated content is written to eligible source notes; a successful result is moved to the reported complete folder if the destination is free |
| Translation | A matching translated output can be overwritten; default names use _<language>.md |
| Mermaid / formula repair | These modify the selected notes; inspect a small sample and retain a backup |
There is no universal skip/append/replace setting across these tasks. For batch title generation, an existing complete-folder destination prevents the move; it does not mean the preceding generation was skipped. The result distinguishes generated and moved counts.
Concurrency Control
Keep batchConcurrency at 1 until a representative sample succeeds. Some batch paths also require enableBatchParallelism before using parallel scheduling; folder translation uses its concurrency setting directly. More concurrency increases provider, memory and local-server pressure, and is not a guarantee of faster completion.
An API interval and batch inter-delay can reduce bursts. They cannot guarantee avoidance of request/token quotas, account limits or other applications sharing the same endpoint.
Configuration
| Setting | Default | Effect |
|---|---|---|
batchConcurrency | 1 | Requested concurrency on applicable batch paths |
enableBatchParallelism | false | Enable parallel scheduling where supported |
batchSize | 50 | Group size used by batched scheduling paths |
batchInterDelayMs | 1000 | Delay between scheduled groups where applicable |
apiCallIntervalMs | 500 | Interval used by concurrent request scheduling |
folderTaskIncludeSubfoldersMode | legacy | Preserve each task's default subfolder scope |
enableStableApiCall | false | Explicit stable request mode |
Per-Task Models in Batch
A folder action uses the same task-specific provider/model choices as the related single-file task. Check them before processing private content. Optional local knowledge retrieval for batch title generation uses one snapshot built at the start of the batch, so edits during that run are not silently mixed into later retrieval results. Start a new batch to include those edits.
Example
Create a trial-titles folder with two title notes and no unrelated files. Run Batch generate from titles, review the generated content and the reported trial-titles_complete destination, then check generated/moved/error counts. If a file failed, diagnose that file before rerunning; rerunning the original folder is not an automatic resume of precisely the unfinished work.
Cancellation And Recovery
Cancel stops new scheduled work and propagates cancellation to supported requests. Calls or writes already accepted by an external system may finish; remote billing is controlled by that provider. Wait for the batch to settle, then inspect completed files and any recovery/conflict paths. Preserve recovery outputs until you have compared them with the current note.
Tips
- Use folder-selection profiles only after validating their actual matched files.
- Reduce concurrency and inspect provider quotas for 429 errors.
- Treat cancellation, failure and completion as distinct outcomes.
- Keep an untouched sample and backup before any operation that modifies existing notes.
Next Steps
- Workflows: chain tasks with explicit failure handling.
- Configuration: output paths and settings defaults.
- Troubleshooting: diagnose an individual failed file.