Email Events API Internal Error


#1

I keep getting an ‘internal error’ for API calls that have worked for months now in an automated workflow. Any idea what could be causing this? The variables in the endpoint are dynamically created and don’t fail until hitting the Email Events API.

Here is the endpoint (key removed):

https://api.hubapi.com/email/public/v1/events?hapikey={apikey}&campaignId=29398013&appId=113&limit=1000

It returns the following error:

message: internal error
correlationId: 9c966b37-3266-4135-abfd-1993629139b8
requestId: c4b4c5c0-a006-482c-a2b7-e293380159cd

This is happening for the majority of the endpoints being called. Nothing has been updated or changed and has been working for months now. I can send Hub ID (and other example endpoints) if needed.

Bryan


#2

Even stranger…the endpoint above just worked while others still failed. In other words, whether or not the endpoint fails seems to be inconsistent which suggests it’s not the endpoint itself causing the error.

Bryan


#3

Hi @Bryan_Girkins

Can you send me your Hub ID so I can take a look at your data? I wasn’t seeing this looking at a few test portals. Also, if you do have other endpoints you saw this with can you send me an example or two as well?


#4

It seems to have resolved itself as I received no errors over night. So I think I’m all clear!

Bryan


#5

@Bryan_Girkins glad to hear that is working again, but if you see those errors again please let us know.


#6

Related, but slightly different. My API calls have increased in duration by a SIGNIFICANT amount. On 12/15, something happened with this API. Prior to my evening API call on 12/15, the average duration of all my API calls was 12 minutes and 49 seconds.

However, starting with my evening API call on 12/15, the average duration increased to 144 minutes!!! This is no longer an acceptable amount of time. I’m sure I can trim the query, but nothing changed and this is a drastic increase in API download duration.

Any idea what is going on?

Date API Download Time (minutes:seconds)
12/1/2016 11:41
9:40
12/2/2016 13:54
9:10
12/3/2016 11:30
8:30
12/4/2016 10:08
8:32
12/5/2016 12:29
7:17
12/6/2016 11:13
9:01
12/7/2016 16:15
10:28
12/8/2016 15:49
10:31
12/9/2016 17:07
10:34
12/10/2016 14:53
10:08
12/11/2016 13:46
10:23
12/12/2016 16:03
12:25
12/13/2016 18:43
13:07
12/14/2016 27:39:00
13:54
12/15/2016 17:00
168
12/16/2016 108
117
12/17/2016 85
206
12/18/2016 108
151
12/19/2016 209
200
12/20/2016 120
105
12/21/2016 148


#7

@Bryan_Girkins do you have any more details for this? Are you seeing an increase in errors and needing to retry more requests? Or do the individual requests seem to be taking longer?


#8

@dadams No errors anymore…just a massive increase in duration. The workflow makes 28 unique API calls for the 28 campaigns we want to download data on. Those 28 API calls took roughly 12 minutes before but are now taking over two hours. Nothing is different in the workflow. Same campaigns, etc.

If needed, I can provide the 28 API calls and our HubID. But the Excel file in the previous reply shows the massive time increase.


#9

@Bryan_Girkins could you send me your Hub ID so I could take a look at this? Also, are you only making 28 total http requests, or pulling the event data for 28 email campaigns (normally each campaign would require more than 1 request to get all of the data)?


#10

Yes, how should I send it?

Correct, it is an iterative download that will continue to download so long as there is an offset. So 28 individual campaign calls, but like you said, 90% of them iterate at least once. But this has been the case the whole time, so the iterations should not matter.


#11

If you click on my name of picture you’ll get a popup, with a message button on the right. You can use that to message me directly.


#12

Getting hit with the internal errors again. Just today. Hoping it resolves itself.