If there is a change in the underlying processes and/or queues (e.g. adding a new log activity or variable type in the process, changing the
JSON schemas for a queue) whose date is ingested for the Insights dashboards, the corresponding widgets and dashboards reliant on that data are temporarily unavailable.
When such a change occurs, the corresponding table in the Insights cube does not import any new data until the table schema is refreshed, and as this is done outside of the normal cube build schedule it can result in dashboard unavailability for up to 30 minutes. To avoid this disruption in dashboard availability it is recommended that any such changes to your processes or queues only be performed during regular maintenance periods.
If the machines where Insights and Orchestrator are being installed are using different TLS configurations, the Insights installation fails. Ensure that both machines are using the same TLS configuration, with
TLS 1.2 being recommended.
Updated about a month ago