This article will cover common issues you may encounter within the Approve app and how you can troubleshoot them.

This article contains the following sections:

• Approval not sent
• Email not received by an approver
• Insufficient approvers

Approval not sent

Step 1: Check the app sidebar.

If the approval displays a pending state but the approver did not receive an email, please refer to email not received by an approver troubleshooting

If the approval displays an error for insufficient approvers, please refer to insufficient approvers troubleshooting.

If approval displays nothing, please refer to how to automatically start an approval process and troubleshoot the trigger.

If the examples above do not describe your issue, please contact support at support@sweethawk.com and provide the following details:

• Ticket ID
• Approval Definition name (including a screenshot of the definition configuration)
• Date and time of when the approval was sent.
• Description of the app sidebar shows (including a screenshot)
• Scope. Does this impact all approvers and approval definitions or just one?

Email not received by an approver

Step 1: Ensure a 'pending' state displays within the app sidebar.

Step 2: Verify the email was not flagged as spam/junk.

Step 3: Check for any errors with the API. Learn how to do this here.

Step 4: Contact support at support@sweethawk.com and provide the following:

• email address of the approver
• ticket ID and date/time of when the approval was sent.
• approval definition that was used

Insufficient approvers

There are several reasons why you might encounter this error, however, the underlying issue is almost always the same – the app is unable to find sufficient approvers to meet the required responses.

Some of the reasons why you might encounter this error are:

1. You have set the required responses greater than that of the approver pool.

2. You have enabled the option that excludes the sender from the approver pool.

Commonly occurs during testing when you are both the sender and the recipient. You will need to disable this option or assign someone other than yourself as the recipient.

3. You are using a custom ticket field and there is no valid user.

If you set the recipient to reference a ticket/user/organisation field, and that field is either empty or the liquid has not been set correctly, you may encounter this error.

Some things you may wish to check when referencing the following field:

Text field: Since this field relies on manual entry, you may encounter user error where the email was not valid or something else entirely. (e.g a phone number)

Lookup field: Ensure this field is present since user error shouldn't be possible.

Drop-down or Multi-select field: Ensure that each field value has the correct user id assigned. Below is an example of an invalid field value.