The problem is that you're calling exists on a subroutine reference for actions 1 and 2. Why not test for something else, such as a HASH reference or a CODE reference using ref? What about: 

sub get_config_item {
    my( $runmodes, $action ) = @_;
    my $config_item = $runmodes->{ config_item };

    if( ref $runmodes->{ $action } eq 'HASH' ) { # error line
        &{ $runmodes->{ $action }{ subroutine }};
        $config_item = $runmodes->{ $action }{ config_item };
    }
    else {
        &{ $runmodes->{ $action }}
    }

    return $config_item;
}

[download]

Honestly though, this looks to me like a candidate for refactoring, as the contortions that you're now enduring will only get worse as the code expands over time.

"The dead do not recognize context" -- Kai, Lexx

In reply to Re: Testing for existence of subroutine ref? by djantzen
in thread Testing for existence of subroutine ref? by legLess

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.