Try comparing the two field in conjunction with a mod operator. Field a = WF field field b = inc field case when Mod(b-a, 20) = 0 then 'do what you need' end Or if you were just using it in a transition you could leave out the case part. I haven't tested that so the syntax might be off, but that should do the trick.

I think your best bet is to create a ticket and let support take a look at it. They can get hands on and fix your issues.

Task is exposed to script, though. I bet you could create a custom action script to set a task on the customer.

Yeah, I got 669 email alerts for workflow failures last night and another 10 or so when I checked this morning. I assume it's related.

Does a scheduled workflow trigger once per day or every half hour? Is there a way to trigger a scheduler workflow on demand for testing purposes? I didn't see this earlier. Yes, there is a way to trigger a scheduled search on demand. I do this with every big scheduled WF I make. Make a second workflow, on the record type…

You go to the System Information tab on the record that is stuck and hit the cancel button next to stuck workflow in the Active Workflows area.

I'm very confused. My workflow is supposed to set event records from a saved search of expired quotes. It seems that my workflow runs at a random time but only once. I get the following error message via email that I can't decipher. ID : 431965 Invalid reference key [0]. When I run the saved search of expired quotes and…

I'll try that. Negative. All I see are transaction searches in the saved search drop down. Off to create a ticket.

That's unfortunate. Thanks for the heads up.

Yeah their message texts leave something to be desired. I would open a ticket and have support look at it. You say you turned off the WF, but did you make it inactive? Setting it to Not Running didn't work for me. I get the above error when I try to look up a field, usually in a workflow action script, with an internal id…

Excellent, I'm glad that worked for you.

Ok, quick update on this. Support found the answer for me. Turns out that creditholdoverride doesn't resolve in a workflow action. I got the above formula by setting in the visual condition designer Customer: Credit Hold = ON and switching it to custom formula. If you look in the latest records browser you will see…

You can do what you want using just a saved search and not bother with a workflow. In the criteria section place your system notes: field statement. Then, go to the email tab, check Send Email Alerts When Records are Created/Updated, select your recipient (employee or group), check Send on Update and Show Recent Changes.…

Workflow action scripts will still attach the email to the record you are on, if you use an internal id for the to parameter. I have a workflow action script that emails customers (and groups of employees as well as some bcc's) from a proposal and the emails are attached to the proposal. Just a heads up.

You can try setting the condition on the action with the visual builder and select record = company, field = credit hold. That is how I had it. Looking at my post above I see I left that out. I con't seem to get this condition to work. You could also try creating a saved search for customers on credit hold and use that as…

Nobody has any ninja error hunting saved search knowledge?

I created a workflow that looks like this: http://screencast.com/t/205Eyt2D4e The transition shown is pretty much as simple as it can get. It just checks a field to see if it has something in it (Is Not Empty). The field is a custom list, but I have also tried the same thing with a date field. The earlier transitions in…

What events do you have it set on? Is it released? Is it scheduled? Need a little more info.

Scheduled to transition on a saved search with unit Day and interval of 1 (ie every day if criteria met in search). When it transitions to state 2, there is an action that occurs on entry then immediately transitions back to state 1 after that action occurs where it waits for 1 day again I didn't even know you could do…

If the workflow has been attached to a record (read: ran on entity, transaction, etc) you will need to delete (maybe inactivate) the record before you can delete the state. This happens to me all the time while I am building out and testing a wf. This really only works during the build out stage. Once a wf is in production…

Yes trying to debug workflows and custom actions is horrid. I have taken to releasing the action and releasing the workflow to me, ignoring the log, as it's useless, and writing a simple send email line with debugging vars in different sections. Also, it'a fairly easy to set up another workflow that initiates on save the…

If you set all your transitions and actions to trigger on entry that should work. Having said that I am finding that scheduled workflows are buggy still. Well, not just scheduled, actually.

If scripting is required I would imagine it wouldn't be that hard of a script. I wouldn't have to the foggiest how to look up if someone else had a record open, however. Anyone else know?

Ah, I was thinking the fix was for yesterday. That would explain it. I am eagerly looking forward to it; I have two other fairly complex workflows to build and I am waiting until I can be sure that they will work as intended. Thanks Evan. Let me just say that I love that you subscribe to threads you have posted on. I have…

Right, so I have a case open with support (case# 1383315). The support person made a simpler copy of my workflow to see if she could reproduce the behavior and she could. There is obviously a defect with scheduled workflows not exiting as required. Interestingly the workflow will exit if the record is viewed (it does not…

Thanks for the heads up Evan. Will the fix force the workflows to exit, or will manually have to with a mass update?

I wonder if it is getting stuck because I have workflow fields that I am setting. I use these fields in all my states. Should I move the fields to my first state and store the value? Is there a reason to not have fields in the WF itself? That doesn't sound right to me.

Ok, 3 days running and none stuck. I think the fix works. I think what I was seeing earlier this week were instances from prior to the fix. After I manually cleared the 20 something workflows, I haven't seen any since. Thanks again for your help Evan (and NS support). And the devs who fixed it, of course :)

Shoot, why did I think it was Tues that it was going out? I know you are getting tired of me.

Ok, I manually viewed all (as of this morning) 211 records with stuck workflows and waited an hour for the workflow to run a couple times and I am back to 172 records with a stuck workflow. Clearly the fix did not work. I have been added to defect 201271 and it is classified as S2, but this really needs to be fixed. super…