|
For troubleshooting information and support, consult the Knowledge Base. If you require additional information not found in the Knowledge Base or listed below in these release notes, contact Technical Support.
Known issues
Refer to the troubleshooting known issues section below for a list of troubleshooting steps available for some of the known issues in this MicroStrategy release.
Resolved issues
For a complete list of all the issues resolved in this MicroStrategy Analytics Enterprise release, consult the Knowledge Base technical note
.
Troubleshooting known issues
Issues
that have a prefix of S (S#####) are customer cases that can be tracked
through MicroStrategy Technical Support. Those that are prefixed with T
(T#####) are MicroStrategy internal issues. Internal issue numbers do not
correlate to customer case numbers.
- T777437: If you use a merge execution process in a System Manager workflow, you must ensure that each merge execution process is only used once when deploying the workflow. If a logical loop in the workflow causes a specific merge execution to be used more than once in a workflow, the processing of the workflow becomes unresponsive and cannot continue further processing past the second use of the merge execution. To avoid this issue, ensure that any workflow that includes a logical loop does not potentially use the same merge execution process twice. You can achieve this by processing tasks sequentially for any portions of a workflow that require a logical loop, and using split and merge executions to process multiple tasks in parallel only for processes that do not require a logical loop.
|