Job Log Too Large to Index Error

[Support_Josh]

Overview
I am getting the error "Job log too large to index" in my job log. The project looks to have completed as expected. This article explains the cause of the error.

Environment
GoAnywhere MFT - all versions

Resolution
When the above error appears in a job log it means that GoAnywhere MFT has attempted to index the job log in its global search index and failed due to the size of the job log being too large. However, the only effect that this has on the GoAnywhere MFT application is that when using the Global Logs “Search” functionality, the job log will not be included in that search since it cannot be indexed. A user can still get to the job log within the GoAnywhere MFT application by searching the Audit Logs for Completed Jobs as normal.

This behavior is intended to keep the Global Log search as quick as possible to prevent long wait times between a search and the corresponding results.

Notes
Technically, this error indicates a field was too large for a database table max character limit. For example if your source_file_path exceeds 256 characters, GoAnywhere MFT will only store the first 256. It will truncate based on the max characters allowed by that field in the database and cannot build a full entry to index.

Here are the field names and sizes. Your value in your project exceeds size on one of these table entries.

source_file_name = 128
source_file_path = 256
source_server_host = 128
source_server_user = 128
destination_file_name = 128
destination_file_path = 256
destination_server_host = 128
destination_server_user = 128