Documentation
Process settings
Tune how the processing service scans, retries, calls AI services, and runs OCR, and check that it picked up your changes.
Overview
The Process page tunes the processing pipeline that the processing service runs: how often it scans for new files, how it retries failures, how long it waits for AI services, and how it runs OCR. It also shows whether the processing service has read the latest values.
Before you begin
You need the Modify Settings permission.
Open the page
Click Administration in the navigation bar, then click the Process card. If you are already in Administration, click Process in the section bar.
Page layout
1Sync status - when the processing service last read the settings and when saved changes take effect.2Check now - reloads the sync status and the settings.3Summary chips - the number of settings and stages, and the changed or waiting settings when there are any.4Settings table - every setting with its value, limits, and actions, grouped by stage.5Stage - the stage name, such as Scan loop, and what the stage controls.6Edit - opens the edit dialog for the setting.7Reset to default - restores the default value after a confirmation.
Sync status
The status line at the top shows when the processing service last read the settings, for example Processing service synced 24 s ago, and when saved changes take effect. The processing service reads the settings every scan cycle. Point at the title to see the exact time it last read them, in server time.
Other states:
- No sync from the processing service for …: the processing service hasn’t read the settings for more than twice the scan interval. Check that the processing service is running.
- The processing service hasn’t synced yet: the service hasn’t read the settings since they were created.
- Sync status unavailable: the page couldn’t load the status.
Click Check now to reload the status and the settings. Chips under the status line summarize the page, for example 7 settings in 4 stages, 1 changed from default, and the number of changes waiting for the processing service, for example 1 change waiting for the processing service.
Settings table
The settings are grouped by stage. Each row shows:
| Column | Description |
|---|---|
| Setting | The setting name, its description, its key, and when a change applies. |
| Value | The current value with its unit, and a readable form where helpful, for example Up to 4 tries in total. Badges show Changed from default, Waiting for sync, or Applied. |
| Limits | The Default value and the Allowed range. |
| Actions | Edit (pen icon) and Reset to default (circular arrow icon). |
Settings reference
| Stage | Setting | Key | Default | Allowed | What it controls |
|---|---|---|---|---|---|
| Scan loop | Scan interval | MasterDelay | 30 s | 5–3,600 s | How often the processing service checks the import folders for new files. Applies after the current scan cycle ends. |
| Retries | Retry attempts | FileProcessingRetries | 3 attempts | 0–10 | How many times a failed file is retried before it is moved to the errors folder. |
| Retries | Retry interval | RetryDelay | 15 s | 1–3,600 s | The wait between retry cycles for failed files. |
| AI services | AI request timeout | RequestTTL | 1,900 s | 30–7,200 s | How long the processing service waits for a response from the topic, entity, coreference, or relation service. |
| AI services | Health check timeout | HealthCheckTTL | 5 s | 1–60 s | How long the processing service waits for an AI service health check before treating the service as unreachable. |
| OCR | OCR timeout | OcrTimeoutMinutes | 10 min | 1–240 min | The maximum time for OCR text extraction from a scanned document. |
| OCR | PDF OCR resolution | PdfOcrDpi | 300 DPI | 72–600 DPI | The resolution used to convert PDF pages to images for OCR. Higher values recognize text better but take longer. |
Edit a setting
1Value in seconds - the new value, with its unit.2Default, Allowed, and Applies - the default value, the allowed range, and when the change takes effect.3Close - closes the dialog without saving.4Save change - saves the new value.
- Click Edit on the setting row.
- In the dialog, enter the new value. The dialog shows the default, the allowed range, and when the change applies. Invalid values show a message, such as
Must be at least 5. - Click Save change. The button is available only when the value is valid and different from the current one.
The table updates in place; the page doesn’t reload. The row shows Waiting for sync until the processing service reads the new value, then Applied. If you close the dialog with unsaved changes, IntQuest asks before discarding them.
Reset a setting to the default
- Click Reset to default on the setting row. The button is unavailable when the setting already has its default value.
- In the confirmation, click Reset to default.
The processing service picks up the default on its next sync.
Notes
- Each setting says when a change takes effect, for example
After the current scan cycle endsorFrom the next retry cycle. - If a row shows Waiting for sync for a long time, check the sync status and that the processing service is running.