Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

roman_paprotsky's avatar

Migration fails due to "telescope_entries" table

Hi all!

I recently installed Spatie's Multi-tenancy package for my Laravel 7 project, and started using a multi-database approach, having a different database for each of the tenant's using my app. This worked up to recently, but when I attempted to do a new migration I got the following error (appeared out of nowhere!):

SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'telescope_entries' already exists

I checked and I do have telescope installed on my app, but I don't have anything for it in my migrations folder. Also, there is no telescope_entries table in my tenant database! Thus, I tried to remove telescope by doing the following:

  1. Commented out App\Providers\TelescopeServiceProvider::class, in my app.php
  2. Added the following to my composer.json:
"extra": {
        "laravel": {
            "dont-discover": [
                "TelescopeServiceProvider"
            ]
        }
    },

However, I'm still getting the error. So my questions are:

  1. Is there something I need to do to make Telescope adhere to multi-tenancy?
  2. How can I fix this migration error? It feels like the migration is sitting in vendors or something but still being called up eventhough I removed the TelescopeServiceProvider, and I don't know enough yet to sort that out, please help!
0 likes
2 replies
jcasanova's avatar

I have and it helped! thanks @corvs

For those interested, add to your AppServiceProvider::register()

Telescope::ignoreMigrations();

Please or to participate in this conversation.