For example, in our Pulse file, we asked for a specific artifact to be captured. Due to some error in our build, the artifact wasn't generated, so the build failed with:

  Capturing artifact 'QtCore.dll': no file matching 'X:/epoc32/release/gcce/urel/QtCore.dll' exists

In the results for this failing build stage, the "environment" and "command output" artifacts were not created (or at least, were not shown in the web UI). This makes it more difficult to debug what went wrong. As a workaround, for the command output, we can look at the raw logs. AFAICT there is no workaround to see what environment was used for invoking the command.