- Issue created by @xamount
- 🇩🇪Germany marcus_johansson
Just a question before looking into this - "FIELD_NAME" is a placeholder for a random field name, correct?
- 🇹🇹Trinidad and Tobago xamount
Sorry, that's actually the machine name of the AI automator, not field name.
- 🇹🇹Trinidad and Tobago xamount
Seems you need to have at least 2 enabled AI automators to get the issue. With one it works.
This is a blocker for me as config import/export is crucial for a successful deployment, and no workaround exists.
- 🇬🇧United Kingdom MrDaleSmith
I can't recreate the error specified but I do get:
[error] Deleted and replaced configuration entity "field.storage.node.ai_automator_status" [error] Deleted and replaced configuration entity "field.field.node.article.ai_automator_status" [error] Unexpected error during import with operation create for field.field.node.article.ai_automator_status: 'field_config' entity with ID 'node.article.ai_automator_status' already exists.
on a drush si --existing-config for a site with two separate content types with automators set up. The field config all looks OK so I'm not sure why the install process has decided it needs to delete and recreate it.