Maybe this is obvious, but to implement some of the suggestions, you need to determine what 'failure' means. With regular Mechanize, you can check 'status' to see what code you got back. Anything other than 200 is an error of some sort, and you can set up various handlers to react based on different error codes (402, 404, 500, etc.). If it just times out, you can detect that value also.

Trouble is, I'm not sure if the Win32 version sets status the same way the base Mech does. If not, you may need to do some more work to evaluate the results of a 'get'.

In reply to Re: catching failures and retrying by cbrandtbuffalo
in thread catching failures and retrying by mickey

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.