Why an async plug-in that raises InvalidPluginExecutionException does not retry

Create a Dataverse plug-in
Answer Correct answer: B — Dataverse async plug-ins do not automatically retry, so raising an InvalidPluginExecutionException cannot satisfy the retry-on-500 requirement.

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result these questions will not appear on the review screen. You are designing an integration that sends created records from a custom Dataverse table to an exposed REST API. When the REST API is unavailable, you must be able to retry if the response status code is 500. You need to select a solution that meets the requirement. Solution: Register an asynchronous plug-in that makes an HTTP request to the REST API. Raise an InvalidPluginExecutionException that is configured to retry when the request fails. Does the solution meet the goal?

  1. Yes
  2. No Correct Answer
async plugin retry dataverse invalidpluginexecutionexception retry dataverse plug-in retry 500

Community Votes

B
78%
A
22%

78% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

InvalidPluginExecutionException cancels/rolls back the operation; it does not configure retries. Dataverse does not automatically retry asynchronous plug-in executions, so a transient 500 from the REST API will simply fail rather than be retried.

An integration sends created Dataverse records to a REST API and must retry when the API returns 500. The proposed solution registers an async plug-in and raises InvalidPluginExecutionException to trigger retry. Dataverse asynchronous plug-ins do not auto-retry on failure, so the requirement is not met.

Assuming raising an exception 'configures a retry.' Exceptions signal failure, they do not schedule retries. The correct retry pattern uses a durable queue (Azure Service Bus) with a dead-letter queue, not a plug-in exception.

Community Discussion (6 comments)

OlenaChep 👍 1 Selected: B
In task we have: when the Rest API is unavailable. According to documentation: The purpose of the dead-letter queue is to hold messages that can't be delivered to any receiver, or messages that couldn't be processed. Messages can then be removed from the DLQ and inspected. An application might let a user correct issues and resubmit the message. In our situation we have nothing to fix. I think it is conceptually wrong to use a dead letter queue in this case.
Juan0414 👍 1 Selected: A
Yes for me. Documentation states this: Retry an asynchronous plug-in With an asynchronous plug-in step, you can retry when a plug-in fails. The cause of the failure may be due to a network error or some other retriable error calling an external resource. To retry your plug-in, use the InvalidPluginExecutionException(OperationStatus, Int32, String) constructor using the OperationStatus Enum Retry member value. When your plug-in throws this type of exception, the asynchronous service attempts to execute your plug-in four times. If the plug-in execution doesn't succeed within four attempts, the call fails. https://learn.microsoft.com/en-us/power-apps/developer/data-platform/handle-exceptions#retry-an-asynchronous-plug-in
loftuscheek 👍 1 Selected: B
Explanation: Asynchronous plug-ins in Dataverse do not automatically retry upon failure. Even if an InvalidPluginExecutionException is raised, Dataverse does not retry asynchronous plug-ins by default. Retries in plug-ins are only applicable to synchronous transactions within the same execution pipeline. However, the requirement here is to retry when an external REST API returns a 500 status code, which is an external system failure, not an internal Dataverse transaction failure.
busitecgmbh 👍 3 Selected: B
No, if a InvalidPluginExecutionException is raised the process is cancelled and can't be configured to retry.
KucaStonojka 👍 2 Selected: B
Raising an InvalidPluginExecutionException does not fulfill the retry requirement.
sudoaptupgrade 👍 1 Selected: A
Yes, because this time it is configured to retry after raising the exception

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Dataverse asynchronous plug-ins are not automatically retried when they fail. Raising an InvalidPluginExecutionException merely aborts the operation and records the error; it does not instruct the platform to re-execute the step. Therefore the solution cannot guarantee a retry when the REST API returns 500.

Why the Other Options Are Wrong

There is no 'A. Yes' path that is correct here. The false assumption is that an exception triggers retry; in Dataverse it does not. A durable messaging pattern (Service Bus queue plus dead-letter queue) is the supported way to achieve retry semantics.

Community Comment Notes

busitecgmbh (likes=3) states that raising InvalidPluginExecutionException cancels the process and cannot be configured to retry. loftuscheek (likes=1) and KucaStonojka (likes=2) both confirm async plug-ins do not auto-retry by default.

Official Reference

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/plug-ins

Related Analysis

You create a custom page that is used as a contextual dialog

A-Grade

You are developing a Power Platform app. The app must implem

A-Grade

Note: This question is part of a series of questions that pr

S-Grade

Practice All PL-400 Questions

Access 85 questions with complete answers and detailed explanations.

View Full PL-400 Practice Test →

← Back to PL-400 Study Guide