Hey @jude,
The “API key” is actually referring to the model ID here, e.g. post or page or similar, not your project API tokens.
We are currently debugging some potentially related bugs in the migration script generator failing when projects are edited after forking and causing model name conflicts:
- Bug: Autogenerating and running migrations tries to generate schema_migration model twice
- Migration generation order is wrong when using existing fields
At first glance, your issue MAY be similar. We are testing an alpha fix internally, but it’s not quite ready for release yet.
We can see if that might also fix your issue… but to do so, could you please send us (here or at support@datocms.com if you prefer) your project URL and the generated migration script so we can take a more detailed look? With your permission, I’d like to try the fix on a copy/fork of your prod-design-v2 environment to see if it works? (We’d create a new one, like prod-design-v2-datocms-support-test and run the alpha fix there.)
Or if you’d rather wait for a fully tested fix, that’s OK too. We’ll let you know once we finish the investigation and produce an update then.
Sorry about that, and thanks for your patience! We’ll provide an update as soon as we can.