workflow *will not* move to the next assignee

jag339:

First off -- sorry that you're having so many issues. However on the flip side, your testing is very valuable!

When you mean "the task still shows as being not completed" -- its still in the user's task console? or does it disappear from there but the next task never appears in the assigned user's console?

That being said, here's some tips and things to try:

1. Did you clear your Drupal cache? There are certain things in Maestro which we cache so that we're not shuffling through templates and content types each time we fire up the engine.

2. Running the orchestrator through the task console? If not, I would suggest checking "ON" that Maestro config option to get you over testing hurdles. (not recommended for production use though)

3. Do *any* of the test workflows work?

Thanks jag339.

I would certainly start with turning on the option to run the orchestrator through the task console (found in the Maestro Configuration). This way by simply refreshing the task console, the orchestrator will get cranked over once. However as noted, that configuration is not optimal (See the readme) but is fine to get your test flows working.

Either way, it is advisable that you get the sample flows to work. This way you know you've got a good base to begin with (ie, Maestro is configured, Drupal 7 is configured, caches are populated properly etc etc).

No, what you've noted should have not had any effect on the engine. The engine doesn't even look at that flag. The Show In Detail flag is only used when using outstanding tasks. There must have been a collection of steps that helped this along. Clear cache perhaps?

Subscribing

One thing to note that I just learned today is that when you refresh the task console, it only increments the work flow one step. That is, it will not complete every step until the next content type task but it will only advance to the next if condition or set variable task. You just need to refresh the Task Console each time you want to move the process forward.

I couldn't figure out what was causing the hang up in my work flow when I had 2 set process variable tasks back to back and it would only advance one. That's when I realized you need to refresh multiple times to move the pointer. Or just use the cron job. Interesting to note though is to consider that each time cron runs it only moves once so if you have 3 steps before the next content type task and cron only runs every 5 minutes, it will take 15 minutes for your next step to appear. Is that correct Randy?

I had the same problem. I corrected it by turning off the "technical support workflow" module that is included with Maestro. Not entirely sure why that worked but I am able to reproduce the issu.

@haydeniv - there are currently 2 ways to have the orchestrator engine run. Through task console refreshes or through a scheduled cron job. The Dev branch has an updated orchestrator that allows you to run both the orchestrator through cron and through task console refreshes.

Anyhow, I would suggest that you increase the frequency of your orchestrator execution in cron.

We have an orchestrator tuned to continually run through tasks until it runs out of things to execute running at a client site -- however that functionality has not been ported to any branch of Maestro as of yet. It would have to be made generic enough to make it in to maestro for which I need time to make that happen.

@Octomated -- sounds like you may have had a silent error or something.
I would check your logs to see if a PHP error was thrown somewhere that would have caused the flow to halt.

Ditto! This fixed my problem too. BTW, great module, but someone needs to check on why this is the case.