Did you set up your automation correctly, check that its trigger was activated, and it's already capturing and processing events, but for some reason, the information isn't reaching the target app?
​

Probably, your events are failing!
Not sure what to do? Don't worry, this article will show you!
​
​It should be noted that all errors are returned by the target app, that is, the app that received the data. Therefore, in most cases, it's important to understand what the returned error means for the targetapp.
​

The first step to analyze and fix a failed event is knowing where to find it!

For this go to “History (Log)” of your automation, in “My automations”.
​

In the “History (Log)” are all your processed events from the last three months, be they “success”, “failed” or “held”.
​

As you can see, one event was processed successfully, but another one failed, and it's this one we'll talk about.
​

To learn more about the “History (Log)”, you can take a look at the article "What exactly is the History (Log) and how to access it?".
​

Oh, if you get to the “History (Log)” and don’t find any events, this article here can help you: “Did you create an automation and haven't had any events yet?”.
​

The second step to fix a failed event is to analyze the reason for it.
​

Click on the “SHOW HOW TO FIX” button:
​

The error message will then appear inside a red rectangle on the top of the page:
​

You can read the text message in order to figure which field should be fixed for the event to be processed.
​
When you select the first app in the flow (which is the source app) and click on the "Outgoing Data" tab, you will find all the information we receive from the source app and send to the target app. It’s always a good idea to review this information to make sure everything is set up correctly.
​

When selecting the second app or others, you will find the information sent and how it was sent. Additionally, error messages are always returned from this second app.
​

You can read the text message in order to figure which field should be fixed for the event to be processed.
​

Now that you know where to find and how to analyze the error, let's show you how to fix them!
​

As we've mentioned, the reason for error is returned by the target app and, therefore, there can be many reasons for them to occur.
​

Some errors can be fixed directly in the “History (Log)”. Others need to be fixed in the field mapping step, by changing the mapped attributes.
​

It is essential to understand the error to fix it effectively and prevent it from happening again. Below, we have a list of possible errors and how you can fix each of them.
​

It's important to note that, when sending information to the target app, filling in certain fields is required. Therefore, when these fields are not filled in, the target app returns an error.
​

To fix this error:

In this gif, you can see how to fix this error in practice:
​

​Important: Always pay close attention to filling in the information even in the source app! This way, you ensure that all required fields are correctly filled in, and this error will not be happen.
​

Just as filling in some fields in the destination app is required, others still require a specific format and have data validation mechanisms. For example, they validate whether a ZIP code exists, if the Tax number is valid, etc.
​

Thus, if an error related to the format of the information is returned, you should fix the respective field directly in the History (Log):

Imagine that you have already verified the filling in your source app, it's being done correctly and the information is being filled in the correct format. But still, your event keeps failing.
​

If this is happening, access your field mapping and check if the attribute selection is correct.
​

When opening, you will notice that there are specific fields to receive each piece of information. Therefore, it is essential that you do the correct mapping, selecting each attribute in its respective field.
​

Was your automation working perfectly and then suddenly stopped processing your events successfully?
​

It could be that the authentication of your target app has expired!
​

To check this information, you should first click the edit button on your automation:
​

Then, on the "Connect your account" step, you can check if the authentication has expired:
​

If it's red, you can click on "RECONNECT" to reestablish the authentication.
​
We also have an article ready explaining how you can reconnect your account: How to reconnect your authenticated app account.