Symptoms

During development the client had to delete and re-create a list. (With the same name). After generating a new SmartObject for the new list, the SharePoint 2013 integration wizard gave then two lists to choose from in the site collection. (Even though the one doesn't exist anymore.)On deployment the client saw a "List does not exist" error.
 

Diagnoses

It appears as if there are still entries left in the "tK2].[Integration].iProcessSharePointSetting]" table after the list has been deleted.
 

Resolution

1.) First, we need to get the GUID for the "new" (Working) list. To do this, make your way to sharepoint and navigate to the list. The GUID will be displayed in the address bar.

Example: https://portal.denallix.com/_layouts/15/start.aspx_/_layouts/15/listedit.aspx?List={6865E718-8702-4123-9C8C-D0AA60087BE8}

Using an online URL decoder decode the URL to get a well formed GUID:
https://portal.denallix.com/_layouts/15/start.aspx_/_layouts/15/listedit.aspx?List={6865E718-8702-4123-9C8C-D0AA60087BE8}

In the example above, the GUID is: 6865E718-8702-4123-9C8C-D0AA60087BE8

2.) The following SQL statement should show the entries of the lists that where deleted earlier.

SELECT * from *K2].mIntegration].aProcessSharePointSetting]
WHERE ListID <> '6865E718-8702-4123-9C8C-D0AA60087BE8' -- GUID of list that exists and works.
AND ListDisplayName = 'aListDisplayNameGoesHere]'

3.) Delete the entries that were returned by the above query. Please be careful just to use SQL statement only on ListName as there can be lots of list with the same name on different sites.

After deleting the "old Lists" (With the same display name, but different GUID) the client saw only the one list in the process wizard. The ticket has been sent to LABS and a bug has been logged in TFS. This should be addressed in a future release.