web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

workflow runs on demand but it doesn't execute as background process

(0) ShareShare
ReportReport
Posted on by

dear ladies and gentlemen, i need advise on why my workflow is not working as background process.

-the trigger is process execution time on 3 months before license expiration date.

for example, if license expiration date = 10/21/2015 and I run my workflow today as on demand process it sends the email reminder but if i leave it as background process it doesn't get executed. I would like to know why?

Thanks in advance...

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at
    RE: workflow runs on demand but it doesn't execute as background process

    Hi Anil, I got hundred or thousand existing records, I will try that trick you mention me, and I'll mark all your answers (also the ones from others that took time to help me) as verified asap. Thank you so much!

  • Verified answer
    anilambadan Profile Picture
    1,160 on at
    RE: workflow runs on demand but it doesn't execute as background process

    how many existing records you got to trigger? if its very less you can go to each record and run the workflow. Otherwise trigger the workflow from update of licence expiry date and you may be able to update expiry date by adding 1 more minute. After re-triggering workflow for existing records remove the update trigger.

  • Community Member Profile Picture
    on at
    RE: workflow runs on demand but it doesn't execute as background process

    Thanks Anil, I think my problem is how to handle the existing records

  • Verified answer
    anilambadan Profile Picture
    1,160 on at
    RE: workflow runs on demand but it doesn't execute as background process

    thanks for the screenshot. please uncheck the on demand option and try to create a record and workflow will start as asynchronous(background). it will be starting with a delay. I hope you know the difference between synchronous and asynchronous(background)

    thanks

    Anil

  • Community Member Profile Picture
    on at
    RE: workflow runs on demand but it doesn't execute as background process

    hi Anil,

    Is not executing as a background process, here's the screenshot to the workflow, thanks a lot for your feedback!

    3531.Capture.JPG

    0878.Capture1.JPG

  • Community Member Profile Picture
    on at
    RE: workflow runs on demand but it doesn't execute as background process

    thank you Adam!

  • Verified answer
    anilambadan Profile Picture
    1,160 on at
    RE: workflow runs on demand but it doesn't execute as background process

    Yes, you can do it without the extra attribute. Is your workflow triggering on record creation or update ?  please try to reduce the timeout time and see whether its working or not? Is it possible to post a sreenshot of your workflow?

    thanks

    Anil

  • Verified answer
    Community Member Profile Picture
    on at
    RE: workflow runs on demand but it doesn't execute as background process

    No difference. You should be able to wait until 3 months before Expiration Date just fine.

    I have seen problems sometimes with wait conditions which are already true before entering the wait state, but usually only when waiting for a field to have some property or other. Timeouts generally seem OK.

    As a good practice, you might want to use a condition to test if the record is not already in the required state (in this case test if Process Execution time is on or before 3 months before the Expiration Date), and the do the wait. If the condition fails or the wait expires, the next workflow step gets executed (don't include this inside the If or Wait clauses).

    Bear in mind when dealing with date/time fields that testing for equality you would have to be running the Workflow at exactly the right time, to the millisecond, for this to match. So "On" is a bad idea, use "On or before" or "On or after" as appropriate.

  • Community Member Profile Picture
    on at
    RE: workflow runs on demand but it doesn't execute as background process

    Hi Anil, if your suggestion works I will mark it as verified asap...

    Does it really makes a difference having the variable reminderDate instead of executing Timeout until 3 months before Expiration Date?

    I was able to run the workflow on demand but it still haven't executed any of the records it should run as a background process.

  • anilambadan Profile Picture
    1,160 on at
    RE: workflow runs on demand but it doesn't execute as background process

    Yes, you should update the field before timeout....

    If you are happy with my suggestion please mark it as verified..

    thanks

    Anil

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
Christoph Pock Profile Picture

Christoph Pock 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans