This means you have to decide what to do when a stub is newly generated for a URL/content type combination for which a stub already exists from a previous import. Most of the time, for the sake of keeping the mock API correct you’ll want to overwrite the previous stub, so this is the default behavior set on the dashboard. However, you also have the option of skipping the already created mock APIs and keep the data for those APIs the same as a previous import.