Answers.Body: <p>The section that entry #392 belongs to is called <code>blog</code> and it's <code>Entry URL Format</code> setting is set to <code>blog/{slug}</code>.</p>
  
  <p>You also have quite a few entries (100 to be precise), with their slug set to: <code>snippet</code> generating a URI for that slug of <code>blog/snippet</code>.</p>
  
  <p>That works great for the first one, but when you try to save the 2nd one, Craft sees that <code>blog/snippet</code> is already taken and will start appending numbers to the end to try and find a unique URI like so: <code>blog/snippet-1</code>, <code>blog/snippet-2</code>, etc.</p>
  
  <p>But Craft wants to have a reasonable way to know when to stop trying to find a unique URI, so it will look to the <a href="http://buildwithcraft.com/docs/config-settings#maxSlugIncrement" rel="nofollow">maxSlugIncrement</a> config setting and use that, which defaults to 100 - hence the error you're running into.</p>
  
  <p>You either need to 1) use something to generate more unique entry slug formats - like post date/time or 2) increase the maxSlugIncrement config setting to a higher value.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-13T20:18:34.987Z
Answers.LastActivityDate: 2015-04-13T20:18:34.987Z
Answers.UserDisplayName: Brad Bell
Body: <p>Recently changed the URL format for a section. Now I have a red circle in the upper right and an error message of "resaving blog entries - failed". Trying again results in same error. Any ideas what could be wrong?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-13T01:06:26.737Z
Comments.Text: You might be trying to use a variable in the section path which doesn't exist and is throwing an error. If you haven't already, you may try turning on debug mode in your config file.
Comments.UserDisplayName: Douglas McDonald
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-13T02:17:00.737Z
Comments.Text: You should also check the craft logs and PHP logs for any obvious errors. You can easily access them from /admin/utils
Comments.UserDisplayName: Aaron Berkowitz
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-13T02:33:36.797Z
Comments.Text: Search your `craft/storage/runtime/logs` files for `[error]` or `[warning]` for any related error messages.
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-13T03:59:51.827Z
Comments.Text: Check [How do I fix a "stuck" task?](http://buildwithcraft.com/help/stuck-tasks) for task unsticking help.
Comments.UserDisplayName: Marion Newlevant
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-13T06:09:38.650Z
Comments.Text: @BradBell I get this: Starting step 296 of 301 total steps. in /storage/TasksService.php (235) 2015/04/12 23:06:23 [error] [application] Encountered an error running task 27 (ResaveElements), step 296 of 301: An exception was thrown while trying to save the Entry with the ID “392”: Could not find a unique URI for this element.
Comments.UserDisplayName: Jim Hull
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-13T19:19:46.293Z
Comments.Text: @jimhull what do you see at /admin/entries/SECTION_HANDLE/392?
Comments.UserDisplayName: Aaron Berkowitz
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-13T20:18:03.100Z
Comments.Text: @AaronBerkowitz Page not found. The requested URL was not found on this server.
Comments.UserDisplayName: Jim Hull
Tags: <sections>
Title: Resaving blog entries keeps failing
ThreadText: # Resaving blog entries keeps failing
  
  (Asked by: username_0 on 2015-04-12)
  
  Recently changed the URL format for a section. Now I have a red circle in the upper right and an error message of "resaving blog entries - failed". Trying again results in same error. Any ideas what could be wrong?
  
  **Tags:** sections
  
  > **Comments:**
  > **username_1**: You might be trying to use a variable in the section path which doesn't exist and is throwing an error. If you haven't already, you may try turning on debug mode in your config file.  
  > **username_2**: You should also check the craft logs and PHP logs for any obvious errors. You can easily access them from /admin/utils  
  > **username_3**: Search your `craft/storage/runtime/logs` files for `[error]` or `[warning]` for any related error messages.  
  > **username_4**: Check [How do I fix a "stuck" task?](http://buildwithcraft.com/help/stuck-tasks) for task unsticking help.  
  > **username_0**: @username_3 I get this: Starting step 296 of 301 total steps. in /storage/TasksService.php (235) 2015/04/12 23:06:23 [error] [application] Encountered an error running task 27 (ResaveElements), step 296 of 301: An exception was thrown while trying to save the Entry with the ID “392”: Could not find a unique URI for this element.  
  > **username_2**: @username_0 what do you see at /admin/entries/SECTION_HANDLE/392?  
  > **username_0**: @username_2 Page not found. The requested URL was not found on this server.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2015-04-13. Score: 2 | Accepted answer
  
  The section that entry #392 belongs to is called `blog` and it's `Entry URL Format` setting is set to `blog/{slug}`.
  
  You also have quite a few entries (100 to be precise), with their slug set to: `snippet` generating a URI for that slug of `blog/snippet`.
  
  That works great for the first one, but when you try to save the 2nd one, Craft sees that `blog/snippet` is already taken and will start appending numbers to the end to try and find a unique URI like so: `blog/snippet-1`, `blog/snippet-2`, etc.
  
  But Craft wants to have a reasonable way to know when to stop trying to find a unique URI, so it will look to the [maxSlugIncrement](http://buildwithcraft.com/docs/config-settings#maxSlugIncrement) config setting and use that, which defaults to 100 - hence the error you're running into.
  
  You either need to 1) use something to generate more unique entry slug formats - like post date/time or 2) increase the maxSlugIncrement config setting to a higher value.
  
  
  ---
  
  