Reset trigger state for Logic Apps
Logic Apps have a variety of connectors with triggers which enable to start a Logic App run based on a condition specific to each connector. The connector trigger is typically generating a trigger state query parameter which the Logic App will preserve and send to the next iteration of the trigger poll invocation. This way the file system connector can for instance save in its trigger state the watermark of the changed files it already picked up in previous iterations.
If the processing of some run fails, the first line of defense is to resubmit the run with the failures. In such Logic App run resubmission, the trigger is not called again and instead the first action in the logic app will receive the trigger output previously recorded. As the trigger is not called, the current trigger state is left unchanged and regular logic app trigger runs are undisturbed.
Now sometimes things go stray and you need to 'reset' a connector trigger to its original state so the logic app may reprocess data. While there is no built-in feature for that "nuclear option", it is possible to achieve this with the following workaround (modify the trigger definition to cause a trigger state reset):
- Save a copy of the original trigger definition.
- Modify the trigger definition and save the updated logic app.
- Modify the trigger definition again to restore it to the original trigger definition of step 1. and save the logic app again.
Comments
- Anonymous
June 20, 2019
This blog has been moved off the MSDN platform. Find further content and update at https://www.linkedin.com/today/author/daviburgComments are locked as part of the blog migration, so please reach out to your customer support contact for assistance with Microsoft products and services.