Workflows are sticking around after they end [#2165183]

Workflows are sticking around after they end. The workflow goes through all the step event ends, but says content in under review? I would think it is complete at this point.

It should be acrchive? Yes

Comment	File	Size	Author
	workvariables.jpg	101.53 KB	spellbinder
	completedWorkflow.png	107.61 KB	spellbinder

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

spellbinder CreditAttribution: spellbinder commented 31 December 2013 at 23:09

Category:

Task

» Support request

Comment #2

spellbinder CreditAttribution: spellbinder commented 3 January 2014 at 16:47

Issue summary:

View changes

Comment #3

_randy CreditAttribution: _randy commented 6 January 2014 at 15:11

I'm not quite following what you're saying here. The status of the content may say under review, but the workflow may have been finished.... They're mutually exclusive entities.

The outstanding tasks console in Maestro should show you what tasks are currently running in the engine.

Comment #4

_randy CreditAttribution: _randy commented 6 January 2014 at 15:11

Status:

Active

» Postponed (maintainer needs more info)

Comment #5

spellbinder CreditAttribution: spellbinder commented 6 January 2014 at 16:00

I would think that a completed work flow would be deleted or archived and not set to under review. Just looking for clarity. Is under review so intiator or admin can review completed workflow prior to deleting it?

Comment #6

_randy CreditAttribution: _randy commented 6 January 2014 at 16:07

What you've shown in your attached images is that the "END" task has been executed. That means that specific instance of the workflow has ended and the process gets flagged as "archived". Maestro's work has been done.

The status of content, anything you do to other entities/data in the system, that is all mutually exclusive from Maestro. So if your workflow does something to content, Maestro is oblivious to it as Maestro follows the tasks in the flow pattern -- It does nothing with any other data elements unless one of your tasks in the flow does so.

So when a flow ends, if a node's status flag is set to something, Maestro doesn't touch it.... When a flow ends, if you set a user's status to blocked in a task in the flow template, Maestro doesn't do anything to change that status when done....

So, if the content in your flow shows Under Review, that is the status flag set on that content. Your custom code can do an update query to change the status to something else.

I hope that helps?!