---
title: "Troubleshooting Group Actions"
canonical: "https://servicedesk.maxgeo.com/space/LC/1264058370/Troubleshooting%20Group%20Actions"
format: markdown
---
<u>**Objective:**</u>

1. To determine why a Group Action is not the due date that I had expected (refer **Troubleshooting 4**)
2. To determine why a Group Action is not generating / regenerating (refer **Troubleshooting 1**).
3. To determine why I have a Group Action and a standard Lease Action that both relate to the same thing (**Troubleshooting 4**).
4. To determine why the Group Actions replaces multiple standard Lease Actions - which is not what I want (refer **Troubleshooting 5**).

<u>**Before you start:**</u>

*Where the below requires access to the SQL database, this should only be done by an appropriately experienced and qualified professional.  Should you not have one available, please contact us at servicedesk.maxgeo.com for assistance.*

Before you follow the troubleshooting, you should have confirmed that this is a Group Action (you may think it is, but may not be, so please check).

<u>**Troubleshooting:**</u>

1. Within the software, check that the correct Group has been assigned.  To do this, go the "Reporting Group" tab and reset the grid to ensure you are seeing the latest data.
  - If the Reporting Group has * on either side of the name refer **Problem 2**.
  - If the Reporting Group is not listed post-reset refer **Problem 1**.
2. Within the software, check that the Reporting Group is present and active.  To do this, go to the "Group Reporting" Browser and reset the grid to ensure it contains the latest data.
  - If the Reporting Group is not listed post-reset, refer **Problem 3**.
  - If the Reporting Group does not have "active" ticked post-reset, refer **Problem 2**.
3. Within the software, check that the Action Configures are present and correct.  To do this, from the "Lease" menu select "Group Report".
  - If the relevant Action Configurations are not listed, tick "view archive" at the bottom of the screen.
    - If the Actions you need are archived, refer **Problem 4**.
    - If the Actions you need are not anywhere, refer **Problem 5**.
4. Within the software, open the Action Configuration in the Action Builder and ensure it is configured correctly.
  - If the configuration is not set to supersede an ordinary Lease Action, and it is meant to, refer **Problem 6**.
  - If the Action Configuration arrives at a different date than the current Action, refer **Problem 7**.
  - If the Action Configuration arrives at an incorrect date, refer **Problem 8**.
5. Within the software, check the Action Type that is being superseded, and compare this to the Action Types configured in the relevant Lease Type (ensuring the select the correct Locality).
  - If there are multiple Action Configurations of this Action Type, refer **Problem 9**.

<u>**Problem:**</u>

1. The Reporting Group has not been correctly assigned to the Lease.  Refer **Solution 1**.
2. The Reporting Group is not active, therefore LeaseControl won't generate further Actions associated with this Group.  Refer **Solution 2**.
3. The Reporting Group has not been created.  Refer **Solution 3**.
4. The Action Configurations have been archived, and therefore LeaseControl will not generate the related Actions.  Refer **Solution 4**.
5. The Action Configurations have not been created, and therefore LeaseControl does not have any Actions to generate.  Refer **Solution 5**.
6. The Action Configuration is not currently instructing LeaseControl to replace (supersede) an ordinary Action.  Refer **Solution 6**.
7. Either the Action Configuration has been changed since the Action was generated, or someone has manually adjusted the due date of the Action.  (If you would like to investigate this further, refer **Troubleshooting 6**). Otherwise, if your Action due date is incorrect refer **Solution 7**, or if your Action Configuration is incorrect refer **Solution 8**.
8. Your Action Configuration is incorrect - refer **Solution 8**.
9. LeaseControl has been instructed to replace all Actions of these configurations, as they are of an Action Type you have selected to supersede (replace) - refer **Solution 9**.

<u>**Solution:**</u>

*Where the solutions requires Actions to be recalculated (e.g. the "redo" function) you should be checking all Actions pre- and post-recalculation to determine that all Actions are as they should be, and immediately investigate any descrepancies.*

1. If there are Reporting Groups present that should not be there, delete them.  Then add any new Reporting Groups that are required, and save your changes.
  - If you cannot find the Reporting Group in the list, refer **Troubleshooting 2**.
2. Tick the box "active" against this Reporting Group, then redo Actions on the relevant Leases.
  - If this does not resolve the issue, refer **Troubleshooting 2**.
3. Create the Reporting Group, then the Actions, then add the Group to the Lease, reset the Actions grid and check everything is present and correct.
  - If this doesn't resolve the issue, refer **Troubleshooting 3**.
4. Restore the Action Configurations by right-clicking the relevant Configuration and selecting "restore".  Then redo Actions on the relevant Leases.
  - If this does not resolve the issue, refer **Troubleshooting 4**.
5. Enter the Action Type of the relevant Action in the "Supersedes" field, then redo Actions on the relevant Leases.
6. Confirm the Action Type of the Action Configuration you wish to supersede (replace) with the Group Action, and enter this into the Group Action Configuration within the field "supersede".
7. Redo Actions on the relevant Lease records.
8. Edit the Action Configuration such that it is correct.  You can test this out on 1 affected Lease by redo-ing Actions on this Lease only, then if the configuration is correct, redo Actions on the balance of the affected Leases.
9. Change the Action Type of the ordinary Lease Action Configurations (and if necessary, the Action Type in the "supersede" field of the Group Action Configuration) such that the only Action Configuration(s) being supersede are the ones you *want* to supersede.  Remember:
  - If necessary, you can create a new Action Type.
  - Check the "follow-on" rules of each relevant Action Configuration to ensure that there are no unintended breaks / errors in workflow.