VERA Add-on Error Codes
Please refer to the below table for error codes and additional information to help troubleshoot various VERA error conditions.
VERA Add-On Error Code | User Message | Additional information for Administrators |
1 | The VERA ID is missing from this record. Please try refreshing this record. If the problem remains, please contact an administrator. | The VERA ID is missing even though status is Routing for Approval. This could be due to a lag in the VERA response. |
2 | The VERA ID is missing from this record. Please report this to an administrator. | The VERA ID is missing even though status is Rejected. |
3 | The VERA ID is missing from this record. Please report this to an administrator. | The VERA ID is missing even though status is Approved. |
4 | VERA could not be reached. Please contact an administrator. | The Authentication Token could not be retrieved. Service Account: |
5 | Rejections could not be retrieved. Please contact an administrator. | Rejections were not retrieved from VERA. |
6 | The VERA Status is not correct for this JIRA Issue. Please contact an administrator. | The VERA Status should have been In Progress, but was not. |
7 | The VERA Status is not correct for this JIRA Issue. Please contact an administrator. | The VERA Status should have been Complete, but was not. |
8 | The VERA Status is not correct for this JIRA Issue. Please contact an administrator. | The VERA Status should have been Stopped, but was not. |
9 | The VERA Status is not correct for this JIRA Issue. Please contact an administrator. | The JIRA Status should have been Routing for Approval, but was not. |
10 | The VERA Approval Route could not be parsed. Please contact an administrator. | Something went wrong when parsing the route. Exception: |
11 | Error connecting to the VERA server. Please contact an administrator. | 500 connection code returned from VERA Server when getting the route. Url: |
12 | Error getting the route from the VERA server. Please contact an administrator. | 204 connection code returned from VERA Server when getting the route. Url: |
13 | An access issue occurred. Refresh the page and try again. If the error persists, please contact an Administrator. | 403, forbidden access, connection code returned from VERA Server when getting the route. Url: |
14 | An access issue occurred. Refresh the page and try again. If the error persists, please contact an Administrator. | 401, unauthorized access, connection code returned from VERA Server when getting the route. Url: |
15 | There was a problem loading the VERA Approval Route. Please contact an Administrator. | An unexpected connection code returned from VERA Server when getting the route. Url: |
16 | There was a problem loading the VERA Approval Route. Please contact an Administrator. | An exception occurred when getting the route. Exception: |
17 | There was a problem loading signatures. Please contact an Administrator. | An exception occurred when getting the signatures. Exception: |
18 | There was a problem loading the rejections. Please contact an Administrator. | An exception occurred when getting the rejections. Exception: |
19 | There was a problem loading the VERA Approval Route. Please contact an Administrator. | An exception occurred when getting the context map. Exception: |
20 | VERA could not be reached. Please contact an administrator. | The Auth Token could not be retrieved. Exception: |