Issue
The refresh-autocomplete-blob job may fail with an error similar to the following:
ERROR [tasks-runner:com.lucidworks.apollo.tasks.BlobDownloadExecutor@75]
Task refresh-autocomplete-blob can't download from https://doc.lucidworks.com/autocomplete/5.4/autocomplete_documentation.jsonThis failure prevents the job from completing successfully in Fusion environments that still attempt to retrieve autocomplete data from the legacy documentation endpoint.
Diagnosis
To verify that this issue matches your environment:
Review the Fusion job history for the
refresh-autocomplete-blobtask.Check the job logs for an HTTP 404 or 400 response when accessing the documentation URL.
In some cases, the job may still report a “SUCCESS” status even though the data download failed internally. Review job events or GCP logs to confirm the error.
Environment
Fusion 5.9.0 through 5.9.15
Managed Fusion and self-hosted Fusion deployments on Kubernetes
Cause
This issue occurs because the refresh-autocomplete-blob job retrieves documentation autocomplete data from a deprecated endpoint.
The legacy autocomplete JSON file (autocomplete_documentation.json) is no longer generated or maintained under the current Lucidworks documentation site. As a result, the download URL returns a 404 (Not Found) error.
Engineering has confirmed that the job is tied to the Fusion Admin UI’s built-in documentation search feature, which is being retired. Beginning with Fusion version 5.9.16, this functionality is scheduled for permanent removal.
Resolution
Temporary workaround
Until the feature is fully removed, you can configure the refresh-autocomplete-blob job url to reference the archived documentation URL given below:
https://archivedoc.lucidworks.com/autocomplete/5.4/autocomplete_documentation.jsonThis allows the job to complete successfully in current versions.
Permanent resolution
Starting with Fusion 5.9.16, the documentation search feature in the Admin UI will be replaced with a direct link to the Lucidworks documentation site. The refresh-autocomplete-blob job will no longer exist after this change.
If the job continues to fail after the update, verify that the Fusion deployment has been upgraded to a version where the feature is deprecated, or remove the job from scheduled runs.