Scheduled custom content type nodes removed from forum when go live

Marking critical. My content providers want to burn me at the stake because they have to manually resave scheduled nodes after they go live.

OK... looks like I'll have some trial and error to do to try to figure out what's interfering.
Thanks.

OK, made a test copy of the site. Disabled all contrib modules except Simple Menu, Scheduler and Contrib Toggle.
Repeated earlier steps. Got same result.
When the node goes live, it's row is removed from the forum table and it does not appear in the forums.

At this point I don't know if there's a bug in the module or something broken with my site. Don't know what to look at next.

Edit: created a new content type and test that in the same way. Same result.
However, the Forum Topic content type works properly.
(I'd just use Forum Topic and promote to front page, but we need separate permissions so our articles are not editable by the wrong people)

FWIW, this also seems to be affecting the sort order of the nodes in forums. That is, after re-saving them to get them back into the forum table, they do not sort to the top of the table. Thought this was a Forum issue, but appears not.

I think you're probably right, but I much apprec. any help tracking it down. Scheduled forum-enabled custom nodes just happens to be where whatever the trouble is shows up.

It must be happening somewhere in that save process... I've also got a hunch it has something to do with taxonomy. Could be all wrong there, but I did observe some slightly different behavior when I messed around w/the vocabularies on these nodes.
- When I did a mass taxonomy change using Views Bulk Options, the changed nodes also lost their presence in the forums table
- When I added a new vocabulary to the Forum Topic node type (bringing the total on those to three including the forums vocab), scheduled nodes that went live appeared as redirects... "This topic has been moved" --or something like that. And it would show under one of vocab. #2's terms.
- When I removed vocab #2 (which had behaved oddly in a variety of circumstances so didn't want to keep it anyway), scheduled Forum Topics behaved normally when they went live.

Whether all this is related or not I don't know... all they have in common is some kind of resave action that in one way or another affected their presence in the forums.

Unfortunately, I don't know much about the inner workings of Drupal so I haven't a clue what hook or whatever would remove or alter a forum row on save. But I suspect that more than one module uses it and there is something going wrong w/how it works under those conditions.

One other thing... neither Scheduler nor VBO produce the problem result if performed on the forum content type. So I wonder what's different about how that content type is saved or how it relates to the forum vocab. vs. other node types.

Did a fresh install of D6.13.
Enabled Scheduler
Enabled Forum
Created new content type (article)
Enabled scheduling in article type
Created new vocabulary (tags)
Enabled tags vocab for article type
Enabled forum vocab for article type
Created new article & scheduled
Ran cron
New article displays on front page. Does not appear in assigned forum. (Forum table has no rows at all)

This did turn out to be a bug in the forum.module.
I posted a for-hire on a solution and got one in the form of a patch to the core.
So more info will appear soon here: http://drupal.org/node/518526