CMS Development

CJohnsonPiano
Contributor

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

I have a ticket outstanding on this as well but want to try to get to the bottom of it and leave a trail for future users to get a possible answer since there are no current search results on the actual error message.

 

Sorry. The following error occurred when importing your file:

Import did not complete within expected time.

 

This started happening recently after mapping all columns for an import and interestingly, would not even reimport the data that's currently in the HubDb, ie export current contents and try to import (we do a replacement of data on a regular basis - and all data is from a recent import). Something changed in import processing in May 2024.  Anyone have a clue?  

1 Accepted solution
CJohnsonPiano
Solution
Contributor

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

The Support ticket on this error yielded the following information - and we are back to a successful import.  Note, it does not appear that the presence of a script tag breaks the import!  

 

From what the team has shared the fix was to a backend rule on one of our networks that was in place that was interfering with the import for your account. Since the change is now in place on our end we don't expect to the see the issue again but will keep on ear and eye just in case.

In this scenario the HAR file captured the error that sent the team in the right direction with their investigation so it was not affected by any scripts and or changes you made on your end. I do see the mention of potential issues with scripts on thread and when I provided the script to the internal team they didn't express any concerns with the script during import. It possible that the fix in place addressed the issue mentioned in the thread about using HTML but the team did not share exact details on any changes put in place. I would suggest going forward continuing with the import as you normally do and to reach out again if you continue to see issues. In case you want to review other limitations going forward here a link to the current documentation.

View solution in original post

10 Replies 10
CJohnsonPiano
Solution
Contributor

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

The Support ticket on this error yielded the following information - and we are back to a successful import.  Note, it does not appear that the presence of a script tag breaks the import!  

 

From what the team has shared the fix was to a backend rule on one of our networks that was in place that was interfering with the import for your account. Since the change is now in place on our end we don't expect to the see the issue again but will keep on ear and eye just in case.

In this scenario the HAR file captured the error that sent the team in the right direction with their investigation so it was not affected by any scripts and or changes you made on your end. I do see the mention of potential issues with scripts on thread and when I provided the script to the internal team they didn't express any concerns with the script during import. It possible that the fix in place addressed the issue mentioned in the thread about using HTML but the team did not share exact details on any changes put in place. I would suggest going forward continuing with the import as you normally do and to reach out again if you continue to see issues. In case you want to review other limitations going forward here a link to the current documentation.

Jnix284
Hall of Famer | Elite Partner
Hall of Famer | Elite Partner

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

This is really good news @CJohnsonPiano, I'm glad to hear that the script wasn't the cause of the issue and am excited to test an import with code again - this will remove a lot of friction for some of the processes I've implemented where code needed to be loaded to HubDB rich text. Appreciate you closing the loop on this! 


If my reply answered your question please mark it as a solution to make it easier for others to find.



Jennifer Nixon - Delivery Lead at Aptitude 8

connect with Jen on Linkedin

0 Upvotes
SteveHTM
Guide | Partner
Guide | Partner

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

@CJohnsonPiano - I have bumped into this time limit on the API call that supports import of a dataset (csv file) into HubDB. My experiences actually date back to the end of last year when I suddenly found that a moderate sized CSV file would no longer import and threw an error similar to the one you report.

 

The time limit of the coded workflow step I used for the import process is 20s - supposedly related to the limits fo a Lambda function on AWS which is used behind the scenes. Actually 20s is a pretty constrianed amount of time for realistic-sized import functions IMHO - and I believe the user community should definitely press for more flexibility here. This is especially true when the startup overhead of any such workflow step can be fairly unpredictable.

 

In my case, after an extended exhange with the support and customer success teams the startup process time did seem to become more predictable - but I am now routinely tracking elapsed time for imports vs record count to try and understand where I might run out if gas as the data set grows. If it's of any interest, here is a simple summary of results seen for my specific HubDB import case at different times of day.

SteveHTM_0-1718146705308.png

Bottom line is that there is no guarantee of any particular performance here - so intermittent failure may be seen as various behind the scenes changes happen. The best we can hope for is accurately reporting our issues in hope of seeing a relaxation of time limits as the demand for such functionality expands.

 

Best of luck,

 

Steve

Steve Christian

HTM Solutions

https://info.htmsolutions.biz/meetings/stevec2

mobilePhone
+1 6195183009
emailAddress
stevec@htmsolutions.biz
website
www.htmsolutions.biz
address
San Diego, CA
Create Your Own Free Signature
CJohnsonPiano
Contributor

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

Steve, Thanks for follow-up/note.   Very interesting test.  Yes, the curious thing about my error is that it is happening almost immediately upon execution of the import step (less than a second for certain) - and I'm only dealing with 70-100 rows of information.  

0 Upvotes
SteveHTM
Guide | Partner
Guide | Partner

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

Here's another thought. I was faced last year with a situation where a HubDB table I has been using repeatly over a long period started to deliver corrupted data rows. Support could not identify an issue, but I was forced to re-create a blank data table and re-import. Even though everything looked identical setup-wise, I had one table that worked correctly and one that repeatedly failed - the same data, just with different table identifiers.

 

So perhaps its worth chasing back to a fresh table just to check for an squirrely issue of that sort? 

Steve Christian

HTM Solutions

https://info.htmsolutions.biz/meetings/stevec2

mobilePhone
+1 6195183009
emailAddress
stevec@htmsolutions.biz
website
www.htmsolutions.biz
address
San Diego, CA
Create Your Own Free Signature
0 Upvotes
SteveHTM
Guide | Partner
Guide | Partner

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

Since you mentoined introducing column mapping for the import at some point along the way, is there any change of data errors getting into the process here? For example, ennumerated type mismatches?

 

Since the error is very opaque I'd be included to systematically cut down your import sheet (column wise) and see if you can isolate a subset that imports correctly. At the very least you will have a better way to report a HubSpot bug with a small dataset.

 

Steve

Steve Christian

HTM Solutions

https://info.htmsolutions.biz/meetings/stevec2

mobilePhone
+1 6195183009
emailAddress
stevec@htmsolutions.biz
website
www.htmsolutions.biz
address
San Diego, CA
Create Your Own Free Signature
CJohnsonPiano
Contributor

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

Some iterative testing shows that a Rich Text column may be the one that causes the import to fail.  It contains varying html and URL content for displaying videos on the website.  

<script src="https://fast.wistia.com/embed/medias/ptad27oxp6.jsonp" async></script><script src="https://fast.wistia.com/assets/external/E-v1.js" async></script><div class="wistia_responsive_padding" style="padding:56.25% 0 0 0;position:relative;"><div class="wistia_responsive_wrapper" style="height:100%;left:0;position:absolute;top:0;width:100%;"><div class="wistia_embed wistia_async_ptad27oxp6 seo=true videoFoam=true" style="height:100%;position:relative;width:100%"><div class="wistia_swatch" style="height:100%;left:0;opacity:0;overflow:hidden;position:absolute;top:0;transition:opacity 200ms;width:100%;"><img src="https://fast.wistia.com/embed/medias/ptad27oxp6/swatch" style="filter:blur(5px);height:100%;object-fit:contain;width:100%;" alt="" aria-hidden="true" onload="this.parentNode.style.opacity=1;" /></div></div></div></div>

 

Jnix284
Hall of Famer | Elite Partner
Hall of Famer | Elite Partner

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

@CJohnsonPiano I can confirm that rich text fields with HTML will cause the import to fail due to spam protection since your code contains scripts.


If my reply answered your question please mark it as a solution to make it easier for others to find.



Jennifer Nixon - Delivery Lead at Aptitude 8

connect with Jen on Linkedin

0 Upvotes
Humashankar
Top Contributor

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

Hi @CJohnsonPiano 

If you're working with a large file, consider breaking it down into smaller, more manageable segments, and give a try and let us know.

 

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

Humashankar VJ
HubSpot Community Champion and enthusiast | Engineering Manager
0 Upvotes
CJohnsonPiano
Contributor

HubDb Import Error: Import did not complete within expected time. Why this error?

SOLVE

As mentioned above in reply to Steve, I'm only dealing with 70-100 rows of information and there is no indication that anything is in a processing lag.  What could be possible reasons?  Breaking down into smaller chunks wouldn't seem to make sense as a solution give the tiny size of the data set.  

0 Upvotes