GTconsult HuntdownaSh4

Who’s the king of the classroom? The Ruler

We had a 2-fold query from a client, either workflows will error randomly or that scheduled workflows does not kick off. We started to look at the Nintex workflow Scheduler timer job. It was either stuck in a running state or it would take anything from 4-12 hours to complete, it should only run for a couple of seconds, every 5 minutes…. where to now.

First we open the Nintex database, and then generate a Usage on disk report on the nw2013 DB. And what a find…. 93k workflow schedules….. that can’t be right….

Second I query the top 1000 rows of the WorkflowSchedule table and found that there where MULTIPLE
schedules for 1 specific workflow… now that doesn’t sound right either, and it was 1218 specifically for the next morning.

I then queried the Workflows database so that I can get the name of the Workflow and the list/site it is associated to.

Short of manually going through 100’s if not 1000’s of lists and site, we call up on good old PowerShell

First we have to get the GUID on the web application where the list is located.

Now that we have webapp ID we can go find our list location, now change the site and enter your list GUID that we got from the SQL query.

Get-SPSite https://sharepoint | Get-SPWeb -Limit ALL | %{$_.Lists} | ?{$_.ID –eq “EADC915D-6DCC-4A39-BC87-45B109A1645F”} | ft Title, ParentWebURL, RootFolder

And there you go, go get that bad bad workflow

Sign Up for a Nintex Demo Now

Leave a Reply

Your email address will not be published. Required fields are marked *