Action errors broken with Statamic 5.26

[caseydwyer]

Description

After upgrading Statmic to v5.26.0, we're seeing odd behavior with Action responses from a Resource CP page—specifically when there's an error. Pretty sure this is related/caused by changes made in Statamic PR #10264.

Did just a tiny bit of diving into this, and wondering if maybe all we need is to update Statamic & recompile assets? Runway's PublishForm.vue appears to import & use Statamic's HasActions.js, which I think might be the key, here, along with the new expectation for a thrown exception, to indicate failure. From changes to ActionController.php in the PR above:

try {
    $response = $action->run($items, $values);
} catch (Exception $e) {
    $response = empty($msg = $e->getMessage()) ? __('Action failed') : $msg;
    $successful = false;
}

Hope that helps, let me know if there's anything else I can do to assist!

Steps to reproduce

1. Open a resource with an available Action
2. Temporarily modify back-end code to throw exception in run method
3. Note the toast is green, indicating a successful action response

Environment

Environment

Environment

Application Name: TF2
Laravel Version: 11.25.0
PHP Version: 8.2.5
Composer Version: 2.5.4
Environment: local
Debug Mode: ENABLED
URL: twenty-for.test
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Statamic

Addons: 6
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.26.0 PRO

Statamic Addons

statamic-rad-pack/runway: 7.10.0

[duncanmcclean]

Thanks! Hopefully it'll be fixed when I tag the next release.

[duncanmcclean]

Would you be able to let me know if it's working for you now?

[caseydwyer]

My apologies, Duncan—should have started higher up the tree. It looks like this is actually an issue with Statamic itself (and the same PR listed above). This issue can stay closed, and here's the PR to patch this (on Statamic's end). Thanks for your help!