Genetec Mission Control™ 3.1.3.0 includes the following known issues.
| Issue | First reported in | Description |
|---|---|---|
| 3422532 | 3.1.3.0 | Triggered alarms from the C•CURE plugin is not displayed in Incident monitoring task. |
| 3419073 | 3.1.3.0 | Changing an incident location to a different map displays the incorrect location, which is not in the new map in Security Desk and Config Tool tasks. |
| 3418673 | 3.1.3.0 | When an alarm is triggered that is associated to a video entity it opens in multiple tiles in the Incident monitoring task. |
| 3417908 | 3.1.3.0 | Uploading documents related to an incident in the Documents widget within the incident details pane does not display the document until the pane is closed and reopened. |
| 3417409 | 3.1.3.0 | When an alarm is triggered that is associated to a video entity it opens in multiple tiles in the Monitoring task. |
| 3417405 | 3.1.3.0 | When an alarm with multiple attached websites is triggered, only one website is displayed when opening the incident in the Monitoring task. |
| 3393927 | 3.1.3.0 | The Shunt reader activity on an incident location does not work on related entities. |
| 3344782 | 3.1.3.0 | In the Incident monitoring task, the entity icon does not change when it is set to maintenance mode. |
| 3339861 | 3.1.1.0 | Incidents with the Auto-open in Monitoring task option enabled does not display the related video unit entity in the Monitoring task. |
| 3295791 | 3.1.1.0 | Document added from the Document management tab in Config Tool does not update dynamically. |
| 3294831 | 3.1.1.0 | Incident triggered with a door as the source does not display the widget. |
| 3292386 | 3.1.0.0 | The Advance event filtering option of an Access granted event for a cardholder does not work when the incident is triggered. |
| 3292385 | 3.1.0.0 | The Wait for event automation activity configured on the Card holder group for Access Granted event is not working. |
| 3245521 | 3.1.1.0 | The Incident monitoring widget is not updated dynamically when changing the name of a document from Document Service page. |
| 3148367 | 3.1.0.0 | Attaching multiple documents to an incident in Security Desk makes the application freeze. |
| 3080516 | 3.0.5.0 | When there are multiple Display entity activities in succession in an automation workflow, video feed from all the entities are not always displayed. |
| 3073253 | 3.0.5.0 | When using Display entity automation activity to display layouts with doors that do not have attached cameras, the doors are not displayed in the Monitoring task. |
| 3066508 | 3.0.4.0 | When the Alarm triggered event is configured as the second trigger for an incident, it does not work even after configuring the Advanced event filtering option. |
| 3054541 | 3.0.4.0 | When sending an email of a snapshot with the Industrial IoT plugin for a custom event, the email received by the recipient does not contain the snapshot. |
| 3020988 | 3.0.4.0 | If an incident is triggered on an Esri map configured with Initial map zoom level for selected incidents, the zoom level cannot be changed on the map. |
| 2989703 | 3.0.4.0 | In the Monitoring task, door entities are missing from the display layout even when the Display entity activity is configured within the automation workflow of the incident. |
| 2936276 | 3.0.3.0 | When an incident is triggered on a custom entity created using a plugin, the incident is not displayed in the Monitoring task. |
| 2922169 | 3.0.3.0 | An active incident triggered by an Access denied event plays live video in the Monitoring task, even when the camera associated with the door is configured for playback. |
| 2835697 | 3.0.2.0 | The Incident report task in Security Desk caps the incident listing at 10,000, even when there are more incidents to be listed. |
| 2806862 | 3.0.2.0 | When there are active incidents triggered on different maps, and the Show all incidents on default map option is selected in the Incident monitoring task dialog box, the map view does not refresh to display an accurate list of active incidents. |
| 2777100 | 3.0.3.0 | When an incident type is configured to trigger an Access denied event followed by the user starting a camera recording, sometimes the trigger rules are not followed. |
| 2736539 | 3.0.1.0 | Genetec Mission Control™ Web API and the Genetec™ Document Service displays the incorrect error code when the document upload request is large. |
| 2563587 | 2.13.3.0 | Outputs from the Mission Control Web API to end users not encoded based on content type. |