Something looks like it's gone wrong with Dream Extractor.  What steps should I take to see if further action is necessary?

Any longer ago than two or three days since an incident and you should talk to Finance in Preston and Tim/Kris in IT in Preston for advice as to what to do next.  The entry may have been manually processed by Finance and we don't want to process it twice so taking no further action could be the right choice.

1. Check the job is running and not stuck in Rundeck.  It should rarely take more than 3 minutes.  If it's been running for over 10, it's almost certainly stuck.  Stop, allow to stop and then restart the Rundeck job and continue checking the below steps.
2. Check the Mantiki Database entity event tables to see if any events are in an error state ie have failed and no processing has occurred (SQL below).  Provided accounts have not manually adjusted for these entries, the state could be set back to pending here and when the extractor runs, it will try and process this entry again.
3. Check the Mantiki Database Dream Extractor temporary tables.  A status of 'Error' indicates that the attempt got so far as to be placed in the Mantiki temporary tables but has failed here.  You can set There's not much point in setting the corresponding entry to pending in the entity event tables but here because the attempt will probably then fail due to a duplicate entry in the temporary table and you may need to remove a failed entry .  Instead, set the record status in the temporary table before setting the entity event to pendingto new to get the record to be reprocessed at this step.
4. If you find errors above, it's unlikely that the entries will have reached the Dream Extractor Sql Server tables.  On taking some of the remedies above you'll want to check that the entry has appeared in the Sql Server tables.  Connection details in the main Dream Extractor guide page.  Also worth checking is that the Sql Server tables contain recent data as if they don't, this is an indication that probably there is a problem (most likely one of the numbers above).

...

1. .

Useful SQL

Find transactions which haven't been processed - eg are either pending (probably legitimately waiting for processing) or are in an error state.

...