You have a few options for disabling remote caching depending on your execution context.

Locally

Option 1.

Run turbo unlink

This will unlink the current repo from the Vercel remote cache. No runs will use the cache unless the repo is relinked

Option 2

Run with --force

This will bypass the cache for any run that includes this argument.

On Vercel

Option 1

Disable globally

The Vercel Remote Cache can be disabled on an account level using the toggle found in account/billing (see the docs for more details)

Option 2

Update your build script to include --force

This will bypass the cache for any run that includes this argument.

In CI

Option 1

Update your build script to include --force

This will bypass the cache for any run that includes this argument.

With that being said, the Prisma issue you're experiencing sounds like it should be investigated separately - would you mind creating an issue for this with some more details?