Definition. A batch conversion workflow repeatedly processes a collection of documents and records the outcome for each source. OfficeAPI supplies offline conversion; your application supplies the queue, file inventory, naming, retry decisions and result reporting. The overview does not define a built-in batch scheduler.
What should a job inventory record?
OfficeAPI's matrix covers 3 office families. Check each source and destination within its family before placing the file in a work queue. Do not derive a valid conversion by combining unrelated input and output rows.
| Application-owned record | Why keep it |
|---|---|
| Source identifier and location | Trace each result to the original document |
| Selected output format and destination | Avoid mixing result types or overwriting sources |
| Current job state | Separate pending, completed and failed work |
| Failure details and retry decision | Revisit individual cases without rerunning everything |
These are suggested application records, not documented SDK fields or engine status codes. Adapt them to the actual integration contract you receive.
How should the workload run?
Use 5 stages:
- Inventory the source files and separate unsupported extensions before starting conversion.
- Check the conversion matrix and define the expected output for each supported family.
- Choose one of the 2 invocation paths and validate a representative sample in the target environment.
- Process jobs while your application records a source-to-result mapping and retains failed cases separately.
- Review results and retry only the cases whose failure conditions have been understood and resolved.
For example, a batch of legacy Word documents may target DOCX, while a collection of Excel workbooks may target CSV. Each needs its own result checks.
How much concurrency should you use?
The product documents publish no concurrency limit, thread-safety contract or throughput benchmark. Do not assume that a native engine means unlimited parallel calls. Consult the integration contract and evaluate CPU, memory, storage and result correctness using your own files before increasing simultaneous work.
Process invocation creates a process boundary, but your application still needs to manage launches and failures. Dynamic library integration shares the application process, so lifecycle and failure handling belong in its integration design.
Where should temporary and final files live?
Choose locations your application is authorized to use and define cleanup after results have been accepted. Keep originals separate from final outputs. A interrupted batch should not leave users unable to determine which files were successfully processed; make that state visible in the application inventory.
Frequently asked questions
Is a cloud connection required for batch conversion?
No connection is required by the OfficeAPI engine. It can run locally or on servers you operate; the application's storage may have its own network requirements.
Does the engine provide automatic retries?
Automatic job retries are not established by the public overview. This guide assigns retry policy to your application.
Can I promise a documents-per-second rate?
Use measurements from your target hardware and documents. The published product sources do not provide such a rate.