Did you set up your automation correctly, see that its trigger was activated, and it's already capturing and processing events, but for some reason, the information isn't reaching the destination app?
Probably, your events are failing!
Not sure what to do? Relax, this article will show you::
- How to find, analyze, and fix a failed event;
- Possible reasons for failure and how to fix each of them;
It should be noted that all failures are returned by the destination app, that is, the app that received the data. Therefore, in most cases, it's important to understand what the returned failure means for the destination app.
How to find, analyze and fix a failed event
1. Finding failed events
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” and/or “held”.
As you can see, some events were processed successfully, but others failed. And it is precisely about them (the ones with failure) that we are going to talk now!
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?”.
2. Analyzing failed events
The second step to fix a failed event is to analyze the reason for it.
Click on the “Fix” button to see the reason for the failure, which is in the red rectangle at the top of the page. See in the image below:
In the left column, are all the information we received from the source app.
In the right-hand column, are the details that were sent to the destination app, according to your field mapping.
It is also in this column that you can check how the information is being sent by Pluga and which field returned an error.
3. Fixing a failed event
Now that you know where to find and how to analyze the failure, let's show you how to fix them!
As we've mentioned, the reason for failures is returned by the destination data app and, therefore, there can be various reasons for them to occur.
Some failures 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 failure to fix it effectively and prevent it from happening again. Below, we have a list of possible failures and how you can fix each of them.
Possible reasons for failure and how to fix each one
Required fields not filled in the destination app
It's important to note that, when sending information to the data destination app, filling in certain fields is required. Therefore, when these fields are not filled in, the destination app returns an error.
To fix this error:
-
Access the “My Automations" page and your “History (Log)”;
-
Find the event with the error and click on “fix”;
-
Properly fill in the required field that caused the error;
-
Click on “Save and Resend” at the end of the page;
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 data app! This way, you ensure that all mandatory fields are correctly filled in, and this error will not be returned.
Incorrectly filled in information sent
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):
-
Access the "My Automations" page and then the "History (Log)" of your automation;
-
Find the event with the error and click on “fix”;
-
Check the format of the information of the field that returned the error;
-
Fill it in with the correct information;
-
Click on “Save and Resend” at the end of the page.
Incorrect field mapping: Too many attributes inserted in one field
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 continues with errors.
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.
Account Authentication Expired
Was your automation working perfectly and then suddenly stopped processing your events successfully?
It could be that the authentication of your destination app has expired!
To check this information, you should simulate creating a new automation and check if the account validation is “green” or “red”. Like this:
If it's red, we already have an article ready for you! Take a look: How to reconnect your authenticated app account.
If you have checked all the above points and none of them apply to your event with the error, please contact our support team by email at support@pluga.co.
Questions?
If you still have questions, just request assistance and our support team will contact you within a few hours ;)