Another possible reason for a 302 besides the record being physically deleted is if you have Assignee Group functionality being used, and the user that tries to access a particular record has no access to that record because of row locking being turned on. I am quite certain you get a 302 when that is the case, as for that user that record is as good as non existent. And I think that is by design as the user has no right to know that record exists.
But as others have pointed out, 90% chance is that record is actually deleted before it is accessed by workflow. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky Sent: Monday, March 17, 2014 4:21 AM To: arslist@ARSLIST.ORG Subject: Re: Entry doesn't exist in Database(302) Hi, Turn on your server logs for API/ESCL/FLTR/SQL and try to find out why you are seeing this. Presumably the record has been removed by an Application-Delete-Entry or Application-Query-Delete-Entry call from an ACTL/FLTR/ESCL between the time the user brings it up on screen in Modify-mode and then hits Save. Search your definitions or logs for the above two delete calls. Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Dears, > please help as I facing a critical issue when alot of users modify some > Tickets and causing to lose data. > Thanks _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
