Building a resilient HttpSend (HttpGet) activity RRS feed

  • Question

  • What is the best practice when using a HttpSend (HttpGet) windows workflow activity to call a web service / web api for hosted office 365 (online) workflows.

    I am mostly interested in retrying errors.

    • I know there is a built in property RetryOnConnectionFailure - what about Http status code like 503 Service Unavailable or 504 Gateway Timeout 
    • There seems to be a built in property ApplyDefaultRetryCodes - but it does not show up in the designer, and there is almost zero documentation around it
    • Is the answer to build our own custom activity and make a do -- while logic around it?
    • Is it possible to use HttpErrorHandler delegate in declarative workflows?

    And finally, where can I find good documentation for Windows workflows?


    Thursday, February 26, 2015 10:59 PM