Katalyst: Uploading Analytical Data from Nested Subfolders

Description

Katalyst and Automation Server support scanning analytical data folders nested within a parent folder, but this functionality requires explicit configuration. By default, the AddOnlyOneSubfolder setting in the Automation Server configuration is set to False, which restricts data uploads to files placed directly in the Scan folder. If this setting is not enabled, attempting to upload data from a parent folder may result in:

• Partial uploads: Only a subset of datasets is processed, while others are removed without being transferred to the Processed or Failed folders.
• Inconsistent folder states: Datasets that fail to process may remain in the original parent folder, while a duplicate parent folder is created in the Processed directory. This can lead to incomplete imports, difficulty tracking failed datasets, and confusion about the state of the data.

When AddOnlyOneSubfolder=True is configured in LC Settings, Katalyst is designed to successfully upload individual .D datasets while leaving the parent folder in the Scan directory. Processed datasets are moved to the Processed or Failed folders as expected.

Solution

Enable nested folder scanning

1. On the Automation Server, open the backend config.ini file.
2. Navigate to the LC Settings section and set:

AddOnlyOneSubfolder=True

3. Save the configuration file and restart the Automation Server service to apply the changes.

Best practices for data uploads

• Place datasets directly under the Scan directory: To ensure predictable processing and file movement, avoid multi-level parent "run" folders. Instead, place individual analytical .D folders directly under the Scan directory.
• Verify instrument and plate mappings: Ensure that well identifiers in the datasets correspond to the defined plate format in Katalyst. Mismatches can result in misattributed or missing runs.
• Monitor processed and failed directories: After enabling nested folder scanning, check the Processed and Failed directories for unexpected behavior (e.g., empty folders, partial uploads). If issues persist, collect the following logs for escalation:
• Automation Server logs (from the Common Logs directory).
• Health Checker logs (from the HealthCheckerLogsDir directory).

Known limitations

• Uploading a parent "run" folder (e.g., containing multiple .D datasets) is not officially supported in the current product version. Until a product update clarifies this functionality, upload specific .D datasets individually to avoid inconsistent behavior.

** Notes**

• This setting is specific to LC data workflows. For other instrument types, consult the relevant configuration sections in config.ini.
• If you encounter persistent issues after enabling this setting, contact Revvity Signals Support with details of the error and logs for further investigation.