>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3537220. --> Reported by: [bisonbleu](https://www.drupal.org/user/549974) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>With <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-14"><a href="https://www.drupal.org/project/ai/issues/3508800" title="Status: Reviewed &amp; tested by the community">#3508800: Adding Disable Option for AI Automators</a></span>, it is now possible to disable automators that use the <strong>Automator Worker: Direct</strong> option.</p> <ul> <li>When an automator is <strong>disabled</strong> in the UI at admin/structure/types/manage/page/automator_chain, saving the node does NOT trigger a call to the LLM;</li> <li>When an automator is <strong>enabled</strong> in the same UI, saving the node triggers the automator i.e. a call is made to the LLM;</li> </ul> <p>This is a great option because it means the field automator configurations can be preserved.</p> <p>But the resulting UX when using the new <strong>Automator Worker: Field Widget</strong> option is less than ideal and somewhat confusing.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>The present issue aims to improve this.</p> <p>Suggestion: maybe by disabling the field widget action button in the edit form i.e. displaying it greyed-out and not clickable. Such a disabled button might be better UX than, say, completely hiding the button, because it informs the user/editor that the automator is configured but disabled.</p> > Related issue: [Issue #3508800](https://www.drupal.org/node/3508800)