SOLVED

Remote Event Receivers - How to guarantee they fire?

%3CLINGO-SUB%20id%3D%22lingo-sub-131999%22%20slang%3D%22en-US%22%3ERemote%20Event%20Receivers%20-%20How%20to%20guarantee%20they%20fire%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131999%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20got%20an%20event%20receiver%20for%20a%20library%20that%20fires%20upon%20ItemUpdated.%20It%20works%20fine%20for%20the%20most%20part%2C%20but%20I%20ran%20a%20mass%20upload%20script%20yesterday%20to%20the%20library%20(about%20800%20items)%2C%20and%20the%20event%20receiver%20doesn't%20seem%20to%20fire%20all%20the%20time%2C%20or%20even%20some%20of%20them%20were%20firing%2C%20but%20doing%20incorrect%20updates%20(it%20appears%20some%20variables%20between%20different%20firing%20events%20got%20mixed%20up....don't%20even%20know%20how%20that's%20possible).%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20question%20is%2C%20is%20there%20a%20recommended%20way%20to%20code%20these%20things%20so%20they%20are%20sure%20to%20fire%3F%20Do%20I%20need%20to%20beef%20up%20the%20power%20on%20my%20azure%20instance%20where%20the%20event%20receiver%20is%20hosted%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20depend%20on%20these%20things%20a%20lot%2C%20and%20previously%20have%20resorted%20to%20writing%20timer%20jobs%20to%20go%20an%20audit%20the%20lists%20where%20event%20receivers%20should%20be%20firing%2C%20but%20this%20doubles%20my%20workload%20anytime%20I%20want%20to%20use%20them.%20I'm%20open%20to%20suggestions!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132058%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Event%20Receivers%20-%20How%20to%20guarantee%20they%20fire%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132058%22%20slang%3D%22en-US%22%3EAFAIK%2C%20thre%20is%20nothing%20you%20can%20do%20to%20ensure%20remote%20event%20receivers%20fire%20correctly....and%20to%20my%20knowledge%2C%20other%20options%20you%20could%20have%20here%20that%20are%20not%20an%20absolute%20guarantee%20for%20scenarios%20where%20there%20is%20a%20massive%20document%20uploads%20are%3A%3CBR%20%2F%3E(1)%20Use%20Webhooks%3CBR%20%2F%3E(2)%20Evaluate%20the%20use%20of%20Flow%20%2F%20Azure%20Logic%20Apps%20for%20your%20scenario%3C%2FLINGO-BODY%3E
Contributor

I've got an event receiver for a library that fires upon ItemUpdated. It works fine for the most part, but I ran a mass upload script yesterday to the library (about 800 items), and the event receiver doesn't seem to fire all the time, or even some of them were firing, but doing incorrect updates (it appears some variables between different firing events got mixed up....don't even know how that's possible). 

My question is, is there a recommended way to code these things so they are sure to fire? Do I need to beef up the power on my azure instance where the event receiver is hosted?

 

I depend on these things a lot, and previously have resorted to writing timer jobs to go an audit the lists where event receivers should be firing, but this doubles my workload anytime I want to use them. I'm open to suggestions!

1 Reply
best response
Solution
AFAIK, thre is nothing you can do to ensure remote event receivers fire correctly....and to my knowledge, other options you could have here that are not an absolute guarantee for scenarios where there is a massive document uploads are:
(1) Use Webhooks
(2) Evaluate the use of Flow / Azure Logic Apps for your scenario