automatic-move-rename is not unpublishing all locations

[esickels]

Hello, when attempting to use the automatic-move-rename workflow, it is not unpublishing from all publishable locations for the asset, specifically, a database. The automatic delete workflow is able to unpublish both our webserver and the database without issue. The publish command is also successful at publishing to both locations. Not sure if I need to specify more information or if this is a bug.

[rgriffith]

@esickels when you have a moment, can you verify if the user who is submitting the move/rename Workflow has access to each of the Destinations via the Applicable Groups?

For a quick test, what you can do is assume that user's identity, visit the asset, and click Publish. Check to see what Destinations are listed under the Destinations section to see if the one you are referring to is listed.

[esickels]

hi @rgriffith ,
Yes, the user has access to the destination. I've also tried assigning an authorizing type like I did for the UnpublishAndDelete trigger in another workflow.

<parameter> <name>authorizing-type</name> <value>user</value> </parameter> <parameter> <name>authorizing-user</name> <value>admin</value> </parameter>

I am not able to assume user identities. I am only a manager for my 30 sites with limited admin options within them.

[rgriffith]

@esickels when you have a moment, try using the following authorization parameter (drop the authorizing-user one) and let me know if this allows the unpublish to go through:

<parameter>
   <name>authorizing-type</name>
   <value>system</value>
</parameter>

[esickels]

Hi @rgriffith -
I've tried the above solution and the table row still remains after the workflow is finished. It does unpublish from the webserver, just not the database.

[esickels]

Hi @rgriffith - when executing the workflow with the authorizing-type set to user, i see this notification in the workflow step:

esickels says: A non-fatal error occurred when executing trigger Publish: The user 'null' cannot publish: The asset is not publishable: Alexander-Niculescu

This is directly under the publish step for unpublishing the asset.

[rgriffith]

Thank you for trying that out @esickels. It looks like your second update may not have been configured properly which ended up with an invalid user attempting to perform the unpublish.

Regardless, checking with my colleagues it appears that you are running into a known defect in which database transports are excluded from the destinations to unpublish from during move/rename/delete operations. That would explain why the asset is removed from all of the destinations except the database one, even with the workflow. This was sort of by design for move/rename, but I can see how that could be problematic for database transports.

Something I'm wondering as a possible workaround is if you try:

• Add a Publish trigger directly before the UnpublishAndDelete trigger which uses the unpublish parameter and a destination parameter that explicitly lists the destination pointing to the database transport. Use the authorizing-type of system
• After the publish trigger, have your UnpublishAndDelete trigger. Use the authorizing-type of system

In theory this should unpublish from that database destination, then unpublish from the remainder of the destinations, and then delete the asset.

Keep me posted on how that goes.

[esickels]

Hi @rgriffith - thanks for the additional info and possible solution. Question for you, are you telling me to add an UnpublishAndDelete trigger to my Move/Copy workflow? The Move/Copy workflow doesn't use the UnpublishAndDelete trigger, so this would be a new trigger. The UnpublishAndDelete trigger that I have referenced is used in our Delete Workflow. When that is used, it gets rid of both the Webserver and Database records for the asset.

I'm just worried about adding UnpublishAndDelete trigger to a move workflow because I don't want the asset to be deleted from Cascade. Could you confirm?

[rgriffith]

@esickels if your goal is to unpublish before completing the move/rename, use the Publish trigger with the unpublish parameter to unpublish the asset before the workflow is completed and the asset is moved/renamed.