Retry When Create file connector in logic app fails first time

Hi @Amit Patel Greetings! Thank you for posting the question here.

If your connector or trigger does not have an inbuilt retry mechanism such as you see for an HTTP action below, there is no simpler way to implement the retry mechanism

You can consider creating an alternate branch in the workflow by configuring the run after setting of an action to trigger if the action has failed and process the event later by sending the file to an Azure storage end point.

The recommended approach to overcome the issue you are facing of throttling errors at the connector is to use unique connections for different actions. You can use the same connection settings and create different connections which will act as a different set of Connector and offer more bandwidth to process the events. If you are facing this error from a for each loop, consider changing the concurrency or parallelism on a "For each" loop.

Please refer the article section Connector throttling for more guidance on this.

Let us know if you need any additional assistance or clarification.

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.