Any errors that occur when sending an AppArmor Alert notification to the Twitter Alerting Mechanism will be logged in the notification’s tracking log. Below are some common errors that you may receive, and some troubleshooting steps you should take before contacting AppArmor Support.
\uD83E\uDD14 401: Unauthorized
A 401: Unauthorized error occurs when the credentials supplied to AppArmor do not match the credentials in your Twitter Developer Portal.
\uD83C\uDF31 Solution
Follow the steps in this article to refresh your Twitter API credentials and input them into the AppArmor Dashboard.
\uD83E\uDD14 403: Forbidden
A 403: Forbidden error occurs when your credentials are correct, but you are trying to access Twitter functionality that you do not have access to. This most often occurs when you are trying to access the incorrect Twitter API version for your credentials.
As a general rule, Twitter API credentials for Twitter Projects or Apps created after April 29th, 2023 should use Version 2 of the Twitter API.
\uD83C\uDF31 Solution
To change the Twitter API Version for your Twitter Integration, follow these steps:
In your AppArmor Dashboard, navigate to the Twitter Alerting Mechanism settings page
Click on the “Modify” button next to the Twitter Integration that is making the error occur
Change the “Twitter API Version” field from whatever it currently is to the other version.
