Workflow task issues
This section describes how to resolve some issues you might see when running a workflow task.
For information on viewing the failures reported by a workflow task, see Task details, status, and results.
Issue | Description/Resolution |
For a workflow that uses an HCP MQE data connection, the task reports 0 documents input. |
Do one of these:
|
A document fails with this message: Document contains at least
one immense term in field="<field-name>" (whose UTF8 encoding is longer than
the max length 32766), all of which were skipped. Please correct the analyzer to
not produce such terms. The prefix of the first immense term is: '[]...', original
message: bytes can be at most 32766 in length; got 953488. Perhaps the document
has an indexed string field (solr.StrField) which is too large |
The field value is too long to be indexed as the currently selected type. In the Index collection schema, select a different type for the field. |
A document fails with this message, instead of a more descriptive error message:
|
This can occur when indexing documents to an index collection with multiple shards. When these failures occur, verify the Caused by section of the error message to see if more details are reported. If you need more information about the failure:
|
A document fails with this message: java.lang.OutOfMemoryError: Java heap space |
The workflow task does not have enough memory. Increase the Driver Heap Limit or Executor Heap Limit setting for the task. |
A task halts with this message:
| |
The Input value on the task Metrics page is higher than expected. |
Possible explanations:
|