Retry logic for Azure transient errors

Occasionally, Azure throws back a "transient error" for issues which have an underlying cause that soon resolves itself. For example, when resources configurations are changing, or a server is spinning up after sleeping (due to a period of non-use).

This results in a TimeXtender error which is not clear (and not always the same) upon deploy / execute / preview. In practice, this means that an extra 'spin up' execution package is needed to access the database (and fail) before a scheduled execution package runs. 

Microsoft details information here about how to implement retry logic in clients that encounter transient errors.

1 comment

Please sign in to leave a comment.