Skip to main content

Get Current Publish Transaction

I was struggling a while back to retrieve the current Publish Transaction from template code. This is the Publish Transaction that is currently being executed in the Publisher. I needed it to identify who sent the current item to publish and with which priority. I found out it wasn't easy to retrieve the current Publish Transaction. In fact, it was impossible to identify it with absolute certainty.

I tried looking at the Publishing Queue and pick the transaction 'In Progress' or with status Rendering. However, this doesn't work reliably due to possible concurrent rendering threads or even multiple Publishers, so it is impossible to know for sure which exactly is the current Publish Transaction.

Then the following hack came to light thanks to a post by Chris Summers. And what a hack it is indeed: take the Binary storage path of the RenderInstruction and extract the Publish Transaction TCMURI from it.

The Binary storage path looks something like C:\Temp\tcm_0-164479-66560.Content\Binaries, so I can apply a Regular Expression to it to extract the TCMURI.

public PublishTransaction GetPublishTransaction(Engine engine)
    String binaryPath = engine.PublishingContext.PublishInstruction.RenderInstruction.BinaryStoragePath;
    Regex tcmRegex = new Regex(@"tcm_\d+-\d+-66560");
    Match match = tcmRegex.Match(binaryPath);

    if (match.Success) {
        String transactionId = match.Value.Replace('_', ':');
        TcmUri transactionUri = new TcmUri(transactionId);
        return new PublishTransaction(transactionUri, engine.GetSession());

    return null;

In the meantime, I filed an enhancement request on this topic.


Chris Summers said…
Thanks for sharing Mihai - this just saved my ass. I have no idea where that post of mine was (I have little recollection of it), but I had certainly forgotten this trick.

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a