Status changing from Active to Closed randomly.

Found the issue after enabling logdump mode on MySQL...

The issue was (and still is) with cron.php, which whenever it was running was setting the state of "active" for the poll to 0.

mysql-bin.000001 356170 Query 1 356299 use `drupal`; DELETE FROM cache_form WHERE expire != 0 AND expire < 1243980901
mysql-bin.000001 356299 Query 1 356428 use `drupal`; DELETE FROM cache_menu WHERE expire != 0 AND expire < 1243980901
mysql-bin.000001 356428 Query 1 356538 use `drupal`; UPDATE decisions SET active = 0 WHERE nid=108
mysql-bin.000001 356538 Query 1 356669 use `drupal`; DELETE FROM cache_filter WHERE expire != 0 AND expire < 1243980901

Thoughts?...

Thanks.
Richard.

Guess I'm answering my own questions as I go along here...

Found the issue. The Decisions cron hook function has an error in logic. The logic in the cron function expires the poll by adding the duration to the time of the CREATION timestamp for the node, NOT the time the poll "opens". So we created a poll last week, and left it unpublished until Monday, but with the cron job expiring based on the creation date, the poll was closing every time the CRON job was run.

I've taken this statement from decisions_cron in decisions.module:

$result = db_query('SELECT d.nid FROM {decisions} d INNER JOIN {node} n ON d.nid = n.nid WHERE (n.created + d.runtime) < '. time() .' AND d.active = 1 AND d.runtime <> 0');

...and updated it to...

$result = db_query('SELECT d.nid FROM {decisions} d INNER JOIN {node} n ON d.nid = n.nid WHERE (d.startdate + d.runtime) < '. time() .' AND d.active = 1 AND d.runtime <> 0');

I'm assuming that every poll will have a start date, or the start date will be set to the creation date where one is not specified...