So the seeds file doesn’t run in production by default. If you need to run them against the production database you’d either need to point your development environment to your production database, or add the yarn rw db seed command to your list of build commands in netlify.toml.
Even though the process is hung, is the database migrated correctly? Or do you still end up with only the _Migration table?
How did you restore the missing migrations? Did you pull them out of git or did you re-create them? We’ve seen issues when Prisma has had new releases where previous migration files generated in beta1 weren’t compatible with beta3, for example. If those migrations were created in previous beta versions of Prisma you may want to delete the migrations directory completely and yarn rw db save to create them from scratch (you’ll end up with 1 large migration that creates all of the tables).