I have a few workflows that handle our weekly reporting process. Everything was working fine, without any errors appearing in the logs until I added a workflow activity that creates a scheduled event to notify users in a certain group. When this scheduled event is created i see a POE::Kernel erros in the error log.

JT says it could be bc they workflow activity is not configured properly, but Im almost certain that it is.

2007/03/29 15:32:07 - ERROR - spectre.conf - POE::Kernel::_dispatch_event[1013] - CRON: Job globalnoc.webgui.conf-jtwkv8F21Ur8BSDvMe2xjg is not in our queue.

is the error i am seeing as a result of creating the scheduled workflow. 

-ckotil 

I created a new workflow that cleans the file cache , if it reaches 10 bytes. (my staff requires instant gratification when posting/approving reports)

I created a workflow to clean the file cache. 

click add new workflow.

select the clean file cache worfklow.

enabled YES,

singleton no , serial no.

then i edited the workflow commit w/out approval (default workflow) added create scheduled event.

Enabled YES, run once YES,  Workflow clean file cache, priority high, * * * * *.

Then when you commit a change this error appears.

2007/03/29 16:01:07 - ERROR - spectre.conf - POE::Kernel::_dispatch_event[1013] - CRON: Job globalnoc.webgui.conf-ChLU_5jwJUHzwv7Xq5uhag is not in our queue.

always w/ a new workflowID

*****

Then I create a scheduled event in another workflow that is basically a modified commit w/ approval workflow. The scheduled event sends an email to a specified address to remind them to approve the pending version tag. (a custom workflow activity I created), this one is configured as follows.

http://www.plainblack.com/user_contributions/user_contributions/miscellaneous/send-an-email-to-a-specified-address.-webguiversiontag-workflow-activity#P6UyIs23JYKr3BNeOqGHyQ 

enabled YES, run once NO(bc they need to be reminded each day until the tag is no longer marked as pending).  0 5 * * *

Then the notify activity has these properties....

enabled YES, singleton no, serial no.

Im no certain what errors this produces, but I know that it does produce errors. I can search the support forums for the error message *i thitn* or wait until next weeks approval process. 

Also these errors are going to increase in the nexxt couple weeks because we are adding 3 new reports to out websites ( and 3 more workflows containing this reminder scheduled event) 

-ckotil 

Was unable to reproduce with the given steps. Could you try going into the database and running "select * from WorkflowInstance where workflowId='XXX'" where XXX is the workflow ID of one of those error messages (preferably immediately after getting the error message).

You may also want to update to latest release before trying to reproduce. Or try to reproduce on the Demo site.

Closing until reproduction.