Further to exception handling being well supported on CPAN for many years (as pointed out by hippo above), note that an officially endorsed Try-Catch Exception Handling notation was released with core perl 5.34 as an experimental feature.

See also:

• Ten Essential Development Practices by Damian Conway: Throw Exceptions Instead of Returning Special Values or Setting Flags (an essential practice in Perl way back in 2005) - see also Perl Best Practices, Chapter 13, Error Handling.
• Best practices for handling errors by v_melnik (2014)
• SO question about Perl exception handling (2010)

• EyeBall stumps BodBall (Error Handling) (2023)
• New built-in perl5.38 try/catch syntax (2023)

On CPAN:

• Try::Tiny by Karen Etheridge
• TryCatch by Ash Berlin

Update

As mentioned at New built-in perl5.38 try/catch syntax:

• perl v5.34 added try/catch syntax based on CPAN module Syntax::Keyword::Try
• perl v5.36 added "finally" blocks to try/catch, also inspired by Syntax::Keyword::Try
• perl v5.36 added use feature 'defer', allowing you to create defer blocks that run at the time that execution leaves the block it's declared inside (which seems to be inspired by the classic RAII programming idiom)
• use v5.36 implies use strict and use warnings
• use v5.38 implies use feature 'try'

As noted at On Interfaces and APIs:

• Perl 5's "string eval" and "block eval" is an example of violation of the "principle of distinction", aka "different things should look different"

Updated: added more references