ErrorType | Error Id | Error Message | Cause | Solution |
InitVariablesError
| | api_base_url not of expected type: str
| This error is raised when api_base_url is not str. | Edit the value of api_base_url in config.json so it is of type str. |
| api_base_url must match regex: (^http|^https)(:\/\/)[-a-zA-Z0-9@:%._\\+~#=]{1,256}(\.)(service[-]?now)(\.com?$). (e.g.https://dev70590.service-now.com )
| This error is raised when optional value api_base_url does not match the required regex. | Make the value of api_base_url in config.json match the indicated format. |
| api_url_regex is the required field for validating the base url. Specify it in collector definitions
| This error is raised when api_url_regex property is not found in collector_definitions.yaml. | This is an internal issue. Contact with Devo Support team. |
| Required setting. 'api_url_regex' is not of expected type: str
| This error is raised when api_url_regex is defined in collector_definitions.yaml but the format is not str. | This is an internal issue. Contact with Devo Support team. |
| historic_date_timeformat is the required field for validating datetime format. Specify it in collector definitions
| This error is raised when historic_date_timeformat property is not found in collector_definitions.yaml. | This is an internal issue. Contact with Devo Support team. |
| Required setting. historic_date_timeformat is not of expected type: str
| This error is raised when historic_date_timeformat is defined in collector_definitions.yaml but the format is not str. | This is an internal issue. Contact with Devo Support team. |
| Required setting, historic_date not of expected type: str
| This error is raised when optional value historic_date added in config.json is not of type str. | Edit the value of historic_date in config.json so it is of type str. Or leave it empty so the collector starts pulling data N days ago at the current time. |
| Invalid value is provided for the historic_date. Provide the date in %Y-%m-%d %H:%M:%S format
| This error is raised when optional value historic_date does not match the required regex. | Make the value of historic_date in config.json match the indicated format. Or leave it empty so the collector starts pulling data N days ago at the current time. |
| Time format for historic date must be %Y-%m-%d %H:%M:%S. e.g. 2015-03-15 05:35:13
| This error is raised when optional value historic_date does not match the required regex. | Make the value of historic_date in config.json match the indicated format. Or leave it empty so the collector starts pulling data N days ago at the current time. |
| Required setting, credentials not found in user configuration
| This error is raised when the required property credentials is not found in config.json. | Add credentials dictionary in config.json, including client_id and client_secret fields. |
| Required setting, credentials not of expected type: dict
| This error is raised when credentials is defined in config.json but the format is not dict. | Edit the value of credentials in config.json so it is of type dict. |
| Required setting, username not found in user configuration
| This error is raised when the required property username is not found in config.json, into credentials dictionary. | Add username property in config.json, into credentials dictionary. |
| Required setting, username not of expected type: str
| This error is raised when username is defined in config.json but the format is not str. | Edit the value of username in config.json, into credentials dictionary, so it is of type str. |
| Required setting 'password' not found in user configuration
| This error is raised when the required property password is not found in config.json, into credentials dictionary. | Add password property in config.json, into credentials dictionary. |
| Required setting 'password' not of expected type: str
| This error is raised when password is defined in config.json but the format is not str. | Edit the value of password in config.json, into credentials dictionary, so it is of type str. |
| 'event_fetch_limit_in_items' is the required setting. Please specify it in collector definitions
| This error is raised when event_fetch_limit_in_items property is not found in collector_definitions.yaml. | This is an internal issue. Contact with Devo Support team. |
| 'event_fetch_limit_in_items' is not of expected type: int
| This error is raised when event_fetch_limit_in_items is defined in collector_definitions.yaml but the format is not int. | This is an internal issue. Contact with Devo Support team. |
| 'event_fetch_limit_in_items' should be in the range 1 to 10000
| This error is raised when event_fetch_limit_in_items is defined in collector_definitions.yaml but the format is not in range 1 to 10000. | This is an internal issue. Contact with Devo Support team. |
| 'user_agent' is the required setting. Please specify it in collector definitions
| This error is raised when user_agent property is not found in collector_definitions.yaml. | This is an internal issue. Contact with Devo Support team. |
| 'user_agent' is not of expected type: str
| This error is raised when user_agent is defined in collector_definitions.yaml but the format is not str. | This is an internal issue. Contact with Devo Support team. |
| default_historical_poll_days is the required field in case historic_date_utc is not specified. Specify it in collector definitions
| This error is raised when default_historical_poll_days property is not found in collector_definitions.yaml. | This is an internal issue. Contact with Devo Support team. |
| Required setting. default_historical_poll_days is not of expected type: int
| This error is raised when default_historical_poll_days is defined in collector_definitions.yaml but the format is not int. | This is an internal issue. Contact with Devo Support team. |
| 'retry_after_sec' is the required setting. Please specify it in collector definitions
| This error is raised when retry_after_sec property is not found in collector_definitions.yaml. | This is an internal issue. Contact with Devo Support team. |
| 'retry_after_sec' is not of expected type: int
| This error is raised when retry_after_sec is defined in collector_definitions.yaml but the format is not int. | This is an internal issue. Contact with Devo Support team. |
| max_number_of_retries is the required field. Specify it in collector definitions
| This error is raised when max_number_of_retries property is not found in collector_definitions.yaml. | This is an internal issue. Contact with Devo Support team. |
| Required setting. max_number_of_retries is not of expected type: int
| This error is raised when max_number_of_retries is defined in collector_definitions.yaml but the format is not int. | This is an internal issue. Contact with Devo Support team. |
| api_timeout_in_seconds is the required field. Specify it in collector definitions
| This error is raised when api_timeout_in_seconds property is not found in collector_definitions.yaml. | This is an internal issue. Contact with Devo Support team. |
| Required setting. api_timeout_in_seconds is not of expected type: int
| This error is raised when api_timeout_in_seconds is defined in collector_definitions.yaml but the format is not int. | This is an internal issue. Contact with Devo Support team. |
SetupError
| | Failed to check if the provided credentials have valid permissions.
| This error is raised when an unexpected error occurred while checking credentials | If there are previous errors, fix them and if the error continues to appear contact with Devo Support team. |
| The credentials provided in the config.yaml are incorrect. Please provide the correct credentials.
Status code: 401
Error message: <error_message>
| This error is raised when the credentials provided in config.json are not valid. (401 Unauthorized error) | Add the correct username and password fields in config.json, at credentials property. |
| The user is not authorized to fetch data from the ServiceNOW.
Status code: 403
Error message: <error_message>
| This error is raised when the credentials provided in config.json are valid, but the credentials used to access the API have no permissions to create a token. (403 Forbidden error) | Add some credentials in config.json with enough privileges to create a token from the API. |
| The requested URL {response.url} is not found. The URL may have been depreciated"
Status code: 404
Error message: <error_message>
| This error is raised when the credentials provided in config.json are valid, but the authentication endpoint that is being requested to get a token is not found. | This is an internal issue. Contact with Devo Support team. |
| Bad request. Check the message from the server.
Error Message: <error_message>
| This error is raised when the api returns a 400 code that indicates that the server cannot or will not process the request due to something that is perceived to be a client error. | Check if exists malformed request syntax, invalid request message framing, or deceptive request routing) |
| Servicenow instance in Hibernation mode. Sign in to ServiceNow and wake up the instance.
| This error is raised when ServiceNow instance went into hibernation due to inactivity | Go to the ServiceNow developers website and wake up the instance. |
| Unexpected error occurred while checking for permissions of user credentials
| This error is raised when there is a problem with the credentials. | Add the correct username and password fields in config.json, at credentials property. |
PrePullError
| | Kindly enter valid date which is less than the current date
| This error is raised when historic_date is later than the current date. | Go to the config.yaml and enter a historic_date less than the current date |
ApiError
| | Error occurred while fetching {table} table data from serviceNow."
Error message: <error_message>
| This error is raised when an unknown problem occurs with the request. | This is an internal issue. Contact with Devo Support team. |
| The credentials provided in the config.yaml are incorrect. Please provide the correct credentials.
Status code: 401
Error message: <error_message>
| This error is raised when there is a problem with the credentials. | Add the correct username and password fields in config.json, at credentials property. |
| The user is not authorized to {table} table data from the ServiceNOW.
Status code: 403
Error message: <error_message>
| This error is raised when the credentials provided in config.json are valid, but the credentials used to access the API have no permissions to create a token. (403 Forbidden error) | Add some credentials in config.json with enough privileges to create a token from the API. |
| The requested URL {response.url} is not found. The URL may have been depreciated.
Status code: 404
Error message: <error_message>
| This error is raised when the credentials provided in config.json are valid, but the authentication endpoint that is being requested to get a token is not found. | This is an internal issue. Contact with Devo Support team. |
| Unexpected error occurred while checking for permissions of user credentials
| This error is raised when there is a problem with the credentials. | Add the correct username and password fields in config.json, at credentials property. |
| After {max_number_of_retries} retries still getting the too many requests error.
| This error is raised when API requests fail after a number of attempts. | This is an internal issue. Contact with Devo Support team. |
| Connection error occurred. Collector is not able to reach the Internet.
Error message: <error_message>
| This error is raised when when the connection takes a long time. | Check that you have an internet connection. |
| Error occurred while fetching {table} table data from serviceNow.
Error message: <error_message>
| This error is raised when an unknown problem occurs with the request. | This is an internal issue. Contact with Devo Support team. |
