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

(0) Share

Report

Posted on by Community Member

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)

All responses (16)

Answers (6)

Verified answer

Royal King 27,686 on at

Like (1)

Report

Do you have wait condition step to execute 3 months before the expiration date?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Chitra,

No, I was executing it inside a Check Condition. I will try that. Thank you so much, have a great day!

Was this reply helpful? Yes No
Suggested answer

anilambadan 1,160 on at

Like (0)

Report

Hi

Please try to set a timeout (wait) on expiration date. please see the screenshot below.

thanks

Anil

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you Anil! I tried 'Process Execution Time on' without luck, may be I need to wait longer for the background process to execute, I'll try the Timeout until... I keep you posted. I appreciate the help.

Was this reply helpful? Yes No
Verified answer

anilambadan 1,160 on at

Like (0)

Report

Please create a custom attribute (reminderDate) and set the new field as 3 months before expiry date, then set timeout on custom attribute(reminderdate).

thanks

Anil

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for the advice, just to clarify should I set the new field (reminderDate) value inside the workflow prior the execution of the timeout.

Was this reply helpful? Yes No
anilambadan 1,160 on at

Like (0)

Report

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

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

thanks

Anil

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Verified answer

anilambadan 1,160 on at

Like (0)

Report

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

Was this reply helpful? Yes No