KB-1569 "An error occurred while retrieving the report" in Task per Process Model report

Jordan Horwat — Mon, 23 Jul 2018 10:23:29 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 10:23:29 AM

Symptoms

When looking at the Task per Process Model report, the following error appears:

The application server log throws the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

Potential causes of this issue are:

A constant has been created with the same name as a task metric.
The Execution and Analytics engines are out of synchronization and need to be synchronized again.

Action

To fix this issue, first verify if a constant exists with the same name as a task metric. To do so, follow these steps:

Navigate to the Rules tab.
Using the search box, check if a constant with any of these names exist:
- task_avg_completion
- Completion
- task_completion_time
- is_process_ontime
- is_process_overdue
- is_task_favorite
- is_task_ontime
- is_task_overdue
- Lag
- NetCompletion
- NetLag
- NetWork
- process_completion_time
- process_deadline
- process_ee_id
- pm_avg_completion
- pm_avg_lag
- pm_avg_work
- process_start_time
- task_assignee_owner
- task_assignment_time
- task_attributed_to
- task_avg_lag
- task_avg_work
- task_deadline
- task_ee_id
- task_status
- total_completion_time
- total_lag_time
- total_work_time
- Work

If a constant with a similar name exists, remove it from the system.

After making sure that no constants exist with a same name as one in the list above, reset the analytics engines. Please refer to KB-1157 How to reset the analytics engines for self-managed installations of Appian for more details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: engines, process models, reports, infrastructure, task

KB-1569 "An error occurred while retrieving the report" in Task per Process Model report

Parmida Borhani — Mon, 30 Apr 2018 02:15:51 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 4/30/2018 2:15:51 AM

Symptoms

When looking at the Task per Process Model report, the following error appears:

The application server log throws the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

Potential causes of this issue are:

A constant has been created with the same name as a task metric.
The Execution and Analytics engines are out of synchronization and need to be synchronized again.

Action

To fix this issue, first verify if a constant exists with the same name as a task metric. To do so, follow these steps:

Navigate to the Rules tab.
Using the search box, check if a constant with any of these names exist:
- task_avg_completion
- Completion
- task_completion_time
- is_process_ontime
- is_process_overdue
- is_task_favorite
- is_task_ontime
- is_task_overdue
- Lag
- NetCompletion
- NetLag
- NetWork
- process_completion_time
- process_deadline
- process_ee_id
- pm_avg_completion
- pm_avg_lag
- pm_avg_work
- process_start_time
- task_assignee_owner
- task_assignment_time
- task_attributed_to
- task_avg_lag
- task_avg_work
- task_deadline
- task_ee_id
- task_status
- total_completion_time
- total_lag_time
- total_work_time
- Work

If a constant with a similar name exists, remove it from the system.

After making sure that no constants exist with a same name as one in the list above, reset the analytics engines. Please refer to KB-1157 How to reset the analytics engines for on-premise installations of Appian for more details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: engines, process models, reports, task

KB-1569 "An error occurred while retrieving the report" in Task per Process Model report

Parmida Borhani — Sun, 29 Apr 2018 22:15:51 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 4/29/2018 10:15:51 PM

Symptoms

When looking at the Task per Process Model report, the following error appears:

The application server log throws the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

Potential causes of this issue are:

A constant has been created with the same name as a task metric.
The Execution and Analytics engines are out of synchronization and need to be synchronized again.

Action

To fix this issue, first verify if a constant exists with the same name as a task metric. To do so, follow these steps:

Navigate to the Rules tab.
Using the search box, check if a constant with any of these names exist:
- task_avg_completion
- Completion
- task_completion_time
- is_process_ontime
- is_process_overdue
- is_task_favorite
- is_task_ontime
- is_task_overdue
- Lag
- NetCompletion
- NetLag
- NetWork
- process_completion_time
- process_deadline
- process_ee_id
- pm_avg_completion
- pm_avg_lag
- pm_avg_work
- process_start_time
- task_assignee_owner
- task_assignment_time
- task_attributed_to
- task_avg_lag
- task_avg_work
- task_deadline
- task_ee_id
- task_status
- total_completion_time
- total_lag_time
- total_work_time
- Work

If a constant with a similar name exists, remove it from the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: engines, process models, reports, task

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model report

Parmida Borhani — Sun, 29 Apr 2018 22:14:57 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 4/29/2018 10:14:57 PM

Symptoms

When looking at the Task per Process Model report, the following error appears:

The application server log throws the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

Potential causes of this issue are:

A constant has been created with the same name as a task metric.
The Execution and Analytics engines are out of synchronization and need to be synchronized again.

Action

To fix this issue, first verify if a constant exists with the same name as a task metric. To do so, follow these steps:

Navigate to the Rules tab.
Using the search box, check if a constant with any of these names exist:
- task_avg_completion
- Completion
- task_completion_time
- is_process_ontime
- is_process_overdue
- is_task_favorite
- is_task_ontime
- is_task_overdue
- Lag
- NetCompletion
- NetLag
- NetWork
- process_completion_time
- process_deadline
- process_ee_id
- pm_avg_completion
- pm_avg_lag
- pm_avg_work
- process_start_time
- task_assignee_owner
- task_assignment_time
- task_attributed_to
- task_avg_lag
- task_avg_work
- task_deadline
- task_ee_id
- task_status
- total_completion_time
- total_lag_time
- total_work_time
- Work

If a constant with a similar name exists, remove it from the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: engines, process models, reports, task

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model report

Diaba Konate — Tue, 24 Apr 2018 07:33:36 GMT

Revision 9 posted to Appian Knowledge Base by Diaba Konate on 4/24/2018 7:33:36 AM

Symptoms

When looking at the Task per Process Model report, the following error appears:

The application server log throws the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

One of the cause of this issue can be that:

A constant has been created with the same name as a task metrics.
The Execution and Analytics engines are out of synchronization and need to be synchronized again.

Action

To fix this issue, first verify if a constant exist with the same name as a task metrics. To do so, follow these steps:

Navigate to the Rules tab
Using the search box, check if a constant with any of these names exist:
- task_avg_completion
- Completion
- task_completion_time
- is_process_ontime
- is_process_overdue
- is_task_favorite
- is_task_ontime
- is_task_overdue
- Lag
- NetCompletion
- NetLag
- NetWork
- process_completion_time
- process_deadline
- process_ee_id
- pm_avg_completion
- pm_avg_lag
- pm_avg_work
- process_start_time
- task_assignee_owner
- task_assignment_time
- task_attributed_to
- task_avg_lag
- task_avg_work
- task_deadline
- task_ee_id
- task_status
- total_completion_time
- total_lag_time
- total_work_time
- Work

If a constant with a similar name exists, remove it from the system.

Affected Versions

This article applies to all versions of Appian.

Tags: engines, process models, reports, task

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model report

Diaba Konate — Tue, 24 Apr 2018 07:30:35 GMT

Revision 8 posted to Appian Knowledge Base by Diaba Konate on 4/24/2018 7:30:35 AM

Symptoms

When looking at the Task per Process Model report, the following error appears:

The application server log throws the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

One of the cause of this issue can be that:

A constant has been created with the same name as a task metrics.
The Execution and Analytics engines are out of synchronization and need to be synchronized again.

Action

To fix this issue, first verify if a constant exist with the same name as a task metrics. To do so, follow these steps:

Navigate to the Rules tab
Using the search box, check if a constant with any of these names exist:

task_avg_completion
Completion
task_completion_time
is_process_ontime
is_process_overdue
is_task_favorite
is_task_ontime
is_task_overdue
Lag
NetCompletion
NetLag
NetWork
process_completion_time
process_deadline
process_ee_id
pm_avg_completion
pm_avg_lag
pm_avg_work
process_start_time
task_assignee_owner
task_assignment_time
task_attributed_to
task_avg_lag
task_avg_work
task_deadline
task_ee_id
task_status
total_completion_time
total_lag_time
total_work_time
Work

If a constant with a similar name exists, remove it from the system.

Affected Versions

This article applies to all versions of Appian.

Tags: engines, process models, reports, task

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model report

Diaba Konate — Fri, 20 Apr 2018 06:33:34 GMT

Revision 7 posted to Appian Knowledge Base by Diaba Konate on 4/20/2018 6:33:34 AM

Symptoms

When looking at the Task per Process Model report, the following error appears:

The application server log throws the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

This issue can be caused by one of two things:

A constant has been created with the same name as a task metrics.
The Execution and Analytics engines are out of synchronization and need to be synchronized again.

Action

To fix this issue, first verify if a constant exist with the same name as a task metrics. To do so, follow these steps:

Navigate to the Rules tab
Using the search box, check if a constant with any of these names exist:
1. task_avg_completion
2. Completion
3. task_completion_time
4. is_process_ontime
5. is_process_overdue
6. is_task_favorite
7. is_task_ontime
8. is_task_overdue
9. Lag
10. NetCompletion
11. NetLag
12. NetWork
13. process_completion_time
14. process_deadline
15. process_ee_id
16. pm_avg_completion
17. pm_avg_lag
18. pm_avg_work
19. process_start_time
20. task_assignee_owner
21. task_assignment_time
22. task_attributed_to
23. task_avg_lag
24. task_avg_work
25. task_deadline
26. task_ee_id
27. task_status
28. total_completion_time
29. total_lag_time
30. total_work_time
31. Work

If a constant with a similar name exists, remove it from the system.

Affected Versions

This article applies to all versions of Appian.

Tags: engines, process models, reports, task

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model report

Diaba Konate — Thu, 19 Apr 2018 14:22:47 GMT

Revision 6 posted to Appian Knowledge Base by Diaba Konate on 4/19/2018 2:22:47 PM

Symptoms

When looking at the Task per Process Model report, the following error appears:

On the JBOSS_HOME/standalone/log/server.log file, this error is thrown:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

This issue can be caused by the fact that the Execution and Analytics engines are out of synchronization and need to be synchronized again.

Action

Resetting the Analytics Engines solves this issue. Refer to KB-1157 How to reset the analytics engines for on-premise installations of Appian for more details.

Affected Versions

This article applies to all versions of Appian.

Tags: engines, process models, reports, task

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model report

Diaba Konate — Thu, 19 Apr 2018 13:52:52 GMT

Revision 5 posted to Appian Knowledge Base by Diaba Konate on 4/19/2018 1:52:52 PM

Symptoms

When looking at the Task per Process Model report, the following error appears:

Looking at the JBOSS_HOME/standalone/log/server.log file, you may see the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

This issue occurs when the data in the Execution and Analytics engines get out of synchronization and need to be synchronized again.

Action

Resetting the Analytics Engines solves this issue. Refer to KB-1157 How to reset the analytics engines for on-premise installations of Appian for more details.

Affected Versions

This article applies to all versions of Appian.

Tags: engines, process models, reports, task

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model report

Diaba Konate — Thu, 19 Apr 2018 13:51:50 GMT

Revision 4 posted to Appian Knowledge Base by Diaba Konate on 4/19/2018 1:51:50 PM

Symptoms

When looking at the Task per Process Model report, the following error appears:

Looking at the JBOSS_HOME/standalone/log/server.log file, you may see the following error:

2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
2016-12-15 19:20:53,204 [ajp-/0.0.0.0:8009-4] ERROR com.appiancorp.process.analytics2.display.ProcessAnalyticsReportData - com.appiancorp.kougar.driver.exceptions.Signal: index
java.lang.RuntimeException: com.appiancorp.kougar.driver.exceptions.Signal: index

Cause

This issue occurs when the data in the Execution and Analytics engines get out of synchronization and need to be synchronized again.

Action

Resetting the Analytics Engines solves this issue. Refer to KB-1157 How to reset the analytics engines for on-premise installations of Appian for more details.

Affected Versions

This article applies to all versions of Appian.

Tags: engines, process models, reports, task

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model

Diaba Konate — Wed, 11 Apr 2018 15:49:10 GMT

Revision 1 posted to Appian Knowledge Base by Diaba Konate on 4/11/2018 3:49:10 PM

Symptoms

When looking at the Task per Process Model, the following error appears:

Cause

This issue can occur when the data in the execution and analytics engines get out of sync and need to be re-synced.

Action

Reset the Analytics Engines solves this issue. Refer to this article for more details.

Affected Versions

This article applies to all versions of Appian.

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model

Diaba Konate — Wed, 11 Apr 2018 12:00:56 GMT

Revision 3 posted to Appian Knowledge Base by Diaba Konate on 4/11/2018 12:00:56 PM

Symptoms

When looking at the Task per Process Model, the following error appears:

Cause

This issue occurs when the data in the Execution and Analytics engines get out of synchronization and need to be synchronized again.

Action

Reset the Analytics Engines solves this issue. Refer to this article for more details.

Affected Versions

This article applies to all versions of Appian.

DRAFT KB-XXXX "An error occurred while retrieving the report" in Task per Process Model

Diaba Konate — Wed, 11 Apr 2018 11:51:50 GMT

Revision 2 posted to Appian Knowledge Base by Diaba Konate on 4/11/2018 11:51:50 AM

Symptoms

When looking at the Task per Process Model, the following error appears:

Cause

This issue can occur when the data in the execution and analytics engines get out of sync and need to be re-synced.

Action

Reset the Analytics Engines solves this issue. Refer to this article for more details.

Affected Versions

This article applies to all versions of Appian.