Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4236384
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 21, 20262026-05-21T02:37:54+00:00 2026-05-21T02:37:54+00:00

I have a Workflow I have created and deployed to a Sharepoint 2007 farm.

  • 0

I have a Workflow I have created and deployed to a Sharepoint 2007 farm. When it runs against an item two delay activities I have created fire immediately.

I have setup a callback on the InitializeTimeoutDuration event. Through logs and debug output I can see that it is setting the delay to one hour. However, at the next SP timer job cycle (less than 5 minutes) the events proceeding the Delay activity fire off.

I’m lost here. Any help is greatly appreciated.

Update

Through some digging I was able to determine why this was firing off. Once the workflow started a record gets added to the ScheduledWorkItems table in the SP Content database. However, the “DeliveryDate” on the record is set to the current time while the “Created” date is set to one hour previous. However, the delay I’m using is 2 hours, so neither of these times make sense to me at all. Going to try hardcoding it….

Update 2

Even with a hardcoded duration the times are off. I hardcoded a 2 hour delay in and the “DeliveryDate” is now one hour in the future while the “Created” date is one hour in the past. So at least the difference between them is good.

Update

Well, that’s embarrassing… found the problem. I’m posting it in here for others that may make mistakes like I do. First off, I was not correct in my UTC->local conversion. The times on the database were correct. What was not correct was how I was setting the TimeoutDuration:

// WRONG!
delayActivity.TimeoutDuration = new TimeSpan("1:00:00"); // one hour

what I should have been doing:

// RIGHT!
((DelayActivity)sender).TimeoutDuration = new TimeSpan("1:00:00"); // one hour

once I made that change everything else seems to be fine.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-21T02:37:54+00:00Added an answer on May 21, 2026 at 2:37 am

    Well, that’s embarassing… found the problem. I’m posting it in here for others that may make mistakes like I do. First off, I was not correct in my UTC->local conversion. The times on the database were correct. What was not correct was how I was setting the TimeoutDuration:

    // WRONG!
    delayActivity.TimeoutDuration = new TimeSpan(“1:00:00”); // one hour

    what I should have been doing:

    // RIGHT!
    ((DelayActivity)sender).TimeoutDuration = new TimeSpan(“1:00:00”); // one hour

    once I made that change everything else seems to be fine.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a sharepoint workflow that I created in VS2010, and I've deployed it
I have a workflow created in Sharepoint designer that works fine when manually triggered.
I have created a SharePoint workflow in visual studio , I have extended this
I have created custom workflow and successfully deployed it on Alfresco. I just copied
I have created a document library in sharepoint 2007 and i have enabled incoming
i have created a workflow activity that do give the item creater of a
I have a workflow that is created in code and a variable of type
I have created a workflow, and Im running it via WorkflowInstance.Run(). This workflow has
I have created a custom workflow activity that copies attachments from a case to
I have a workflow running on an item in a list. The workflow has

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.