Trigger errors happen when Workato was not able to poll the trigger app successfully to check if there are any new or updated jobs to be processed.
Trigger errors may occur if your recipe has schema which is outdated. For example, if you had removed custom fields in your app that the recipe was using, the recipe may still request the trigger app for these custom fields from your application, causing the app to respond with an error message. To resolve this, you need to refresh the schema of your recipe.
Similarly, trigger errors may occur if any data set up in the trigger is now outdated. For example, if you had set your trigger up to monitor new files in a Box folder, or new lines in a Google spreadsheet, but subsequently moved that Box folder to another folder, or deleted the Google spreadsheet, the trigger might throw an error as it is trying to monitor something that no longer exists.
Trigger errors may also occur if Workato was not able to connect successfully to the trigger app. This might be because the credentials have changed (e.g. if your username or password was changed in the app, but it was not updated in Workato). To resolve this, you need to reconnect to your trigger app on Workato.
Trigger errors will not count towards transactions, nor will it show up in your jobs history, as no jobs were picked up by the recipe when it encounters trigger errors.