Automator FWA buttons give no user feedback when values don't visibly change
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3585987. -->
Reported by: [petar_basic](https://www.drupal.org/user/3626336)
>>>
<p>[Tracker]<br>
<strong>Update Summary: </strong>[One-line status update for stakeholders]<br>
<strong>Short Description: </strong>[One-line issue summary for stakeholders]<br>
<strong>Check-in Date: </strong>MM/DD/YYYY<br>
<em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br>
[/Tracker]</p>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>When an editor clicks a Field Widget Action (FWA) button backed by an ai_automator, the AJAX call runs, the throbber appears and disappears, but there is no user feedback confirming that the automator actually ran.</p>
<p>This is especially visible on the ClassificationOptionsSelect widget for taxonomy reference fields: </p>
<p> - User clicks Suggest Topic on a field that already has a value selected.<br>
- AI runs and returns the same value that is already selected.<br>
- Form state does not change — dropdown stays on the same option.<br>
- Editor sees nothing happen and assumes the button is broken.</p>
<h4 id="summary-steps-reproduce">Steps to reproduce (required for bugs, but not feature requests)</h4>
<p>Please provide information like AI modules enabled, which AI provider, browser, etc.<br>
1. Install ai_automators and field_widget_actions.<br>
2. Configure an automator with worker_type: field_widget_actions on a taxonomy reference field (e.g. field_topic with a Topics vocabulary).<br>
3. Set up ClassificationOptionsSelect FWA on the form display.<br>
4. Open a node edit form where field_topic already has a value selected.<br>
5. Click the Suggest Topic button.<br>
6. Observe: AJAX runs, throbber shows+hides, nothing else changes on screen. </p>
<p> Same effect when the AI returns the same value already entered on any other automator FWA plugin.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>In AutomatorBaseAction::populateAutomatorValues(), after saveFormValues(), add a status message with the values the automator generated.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<h3>Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes)</h3>
<h3 id="summary-ai-usage">AI usage (if applicable)</h3>
<p>[ ] AI Assisted Issue<br>
This issue was generated with AI assistance, but was reviewed and refined by the creator.</p>
<p>[ ] AI Assisted Code<br>
This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision.</p>
<p>[ ] AI Generated Code<br>
This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human.</p>
<p>[ ] Vibe Coded<br>
This code was generated by an AI and has only been functionally tested.</p>
issue