# Generic actions vs Splode errors

**URL:** <https://forum.elixirforum.com/t/generic-actions-vs-splode-errors/64034>\
**Category:** Questions\
**Tags:** error-handling, ash, splode\
**Created:** [June 7, 2024, 7:42am UTC](https://forum.elixirforum.com/t/generic-actions-vs-splode-errors/64034 "2024-06-07T07:42:33Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![spacebat](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/spacebat/32/25330_2.png) [@spacebat](https://forum.elixirforum.com/u/spacebat)\
**Post date:** [June 7, 2024, 3:09pm UTC](https://forum.elixirforum.com/t/generic-actions-vs-splode-errors/64034/5 "2024-06-07T15:09:43Z")

</div>

I was returning an error tuple from the generic action, like `{:error, :enoent}` but it raised errors about not having the right arguments to construct an Ash.Errors.Unknown.Unknown or something. Figuring I know what this error is, I guess it needs a custom error so I tried adding one by copying the Splode guide but that’s not working out.  
So it seems I need to either add a `:custom` error class to Ash’s error module, or only use an error class that’s already in Ash’s error module, or… I’m not sure what is the use of defining an error class in my app’s error module if it will be passed to Ash which rejects it.

---

_[View the full topic](https://forum.elixirforum.com/t/generic-actions-vs-splode-errors/64034)._