Exceptions
When using MSPintegrations to perform calls to the Autotask API, you may encounter situations where the API call fails or is rejected by Autotask.
Common Reasons for API Call Failures
API calls to the Autotask API can fail due to various reasons, including:
- Autotask API is Unreachable: The Autotask API might be down or experiencing issues.
- Invalid Credentials: The Autotask API credentials stored in MSPintegrations might be incorrect or disabled.
- Incorrectly Formatted API Calls: The API call may be missing required data or include invalid data.
- Quota Exhaustion: The Autotask database may have exhausted its allowed quota for API calls.
What Happens after an Exception Occurs
When an Autotask API call fails, MSPintegrations generates an exception. This stops the current workflow and sends an email notification to the address specified in the MSPintegrations settings
When you receive a notification of an exception, you should try to determine what caused it. You may have a misconfigured rule or action, or the logic in your workflow may be invalid.
You should rectify the issue and then replay the message from your history to verify that it works as intended.