Answers.Body: <p>That's a lot of contacts to import at once. Honestly, I try to keep it below 2,000 an import, especially if there is a lot of information. If you're only allowed a max of 60 seconds, it's likely there are other places where you will also run into errors regarding it timing out. Not only that, I've found that often times even when you think it did import everything, there was indeed information left out, errors with contacts, etc. Long term, your best solution will likely be a new host where you get more control over your resources. Looking at their site, it appears to be more of a shared hosting environment and I've found that I can rarely get a large CiviCRM site running well unless I'm either on a VPS with control over the resources or a dedicated server.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-12-28T20:59:24.970Z
Answers.Text: Even on a different server - and I agree completely about changing the hosting environment - I would still recommend limiting the number of contacts imported, as Jenni wisely advises you.  Better to split the import up into smaller chunks and only have to run it once, than to spend/waste time trying to figure out what imported/didn't import when it times out IMHO.
Answers.UserDisplayName: Lesley Carter - BackOffice
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-12-28T02:07:17.937Z
Answers.LastActivityDate: 2017-12-28T02:07:17.937Z
Answers.UserDisplayName: Jenni Simonis
Answers.Body: <p>If you can access httpd.conf file, add TimeOut value - it dramatically changed the number of records we were able to import - 5x and perhaps more per upload.</p>
  
  <p>The value should be set under Server Root section
  we set as a temporary value to:
  TimeOut 1200 </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-17T22:24:58.040Z
Answers.LastActivityDate: 2020-03-17T22:24:58.040Z
Answers.UserDisplayName: Dave T
Body: <p>Drupal 7 CiviCRM 4.6.28 Hosted on: Pantheon</p>
  
  <p>I have a client that needs to import 15,000-20,000 contacts on CiviCRM. The problem we are running into is that importing any amount over 500 is causing a page timeout error to be thrown; our host, Pantheon, puts a strict 60-second limit on how long a page can take to load. We have been working on getting the resource usage down, which has improved the import, but the error is still being thrown.</p>
  
  <p>The import does continue, and finish the job, after the error is thrown. We need the error to stop being thrown, though, so that the client can be confident that the import has completed.</p>
  
  <p>The current idea we have to fix this is to skip over the import progress bar popup, keep them on the Summary page, and use Ajax to track the import and communicate when it is finished.</p>
  
  <p>I'm fairly new to CiviCRM, so am wondering, does that solution sound doable?  Or, does anyone have an idea for another solution to this problem?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-12-28T05:02:38.160Z
Comments.Text: I can't really speak to the specifics without much more detail that I'm sure you don't have time to sort nor do I to review right now, but I do think that if you were to try this on a server with pretty high resources and good configurations files you could get this done. After that, you could continue to host on that other system or move over to pantheon so from pantheon's side it is a standard import
Comments.UserDisplayName: ericG
Tags: <contacts><import><pantheon>
Title: Page timeout on contact import
ThreadText: # Page timeout on contact import
  
  (Asked by: username_0 on 2017-12-27)
  
  Drupal 7 CiviCRM 4.6.28 Hosted on: Pantheon
  
  I have a client that needs to import 15,000-20,000 contacts on CiviCRM. The problem we are running into is that importing any amount over 500 is causing a page timeout error to be thrown; our host, Pantheon, puts a strict 60-second limit on how long a page can take to load. We have been working on getting the resource usage down, which has improved the import, but the error is still being thrown.
  
  The import does continue, and finish the job, after the error is thrown. We need the error to stop being thrown, though, so that the client can be confident that the import has completed.
  
  The current idea we have to fix this is to skip over the import progress bar popup, keep them on the Summary page, and use Ajax to track the import and communicate when it is finished.
  
  I'm fairly new to CiviCRM, so am wondering, does that solution sound doable? Or, does anyone have an idea for another solution to this problem?
  
  **Tags:** contacts, import, pantheon
  
  > **Comments:**
  > **username_1**: I can't really speak to the specifics without much more detail that I'm sure you don't have time to sort nor do I to review right now, but I do think that if you were to try this on a server with pretty high resources and good configurations files you could get this done. After that, you could continue to host on that other system or move over to pantheon so from pantheon's side it is a standard import  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2017-12-28. Score: 4
  
  That's a lot of contacts to import at once. Honestly, I try to keep it below 2,000 an import, especially if there is a lot of information. If you're only allowed a max of 60 seconds, it's likely there are other places where you will also run into errors regarding it timing out. Not only that, I've found that often times even when you think it did import everything, there was indeed information left out, errors with contacts, etc. Long term, your best solution will likely be a new host where you get more control over your resources. Looking at their site, it appears to be more of a shared hosting environment and I've found that I can rarely get a large CiviCRM site running well unless I'm either on a VPS with control over the resources or a dedicated server.
  
  > **Comments:**
  > **username_3**: Even on a different server - and I agree completely about changing the hosting environment - I would still recommend limiting the number of contacts imported, as username_2 wisely advises you.  Better to split the import up into smaller chunks and only have to run it once, than to spend/waste time trying to figure out what imported/didn't import when it times out IMHO.  
  
  ---
  
  ### Answer by username_4 on 2020-03-17. Score: 0
  
  If you can access httpd.conf file, add TimeOut value - it dramatically changed the number of records we were able to import - 5x and perhaps more per upload.
  
  The value should be set under Server Root section
  we set as a temporary value to:
  TimeOut 1200
  
  
  ---
  
  