Monitor Custom Script Deployments and Execution History (Beta)

Review comprehensive information about your deployment, including status, execution metrics, configuration settings, and performance monitoring.

Code extension is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Beta Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.

Edition Table
Available in: Developer, Enterprise, Performance, and Unlimited Editions. See Data 360 edition availability.
Permission Sets Needed
To monitor a custom code deployment and execution history:Permission set:
  • Data Cloud Architect
  1. In Data 360, go to the Code Extension tab.

    If the Code Extension tab isn’t visible, click More and select Code Extension.

  2. Click any custom code name to see its deployment details.

  3. The Details tab shows comprehensive information about your deployment configuration and metadata.

The Details tab displays the following information about your deployment:

FieldDescription
Deployment NameThe name given to the deployment
Deployment API NameThe unique API name used to reference the deployment programmatically
Deployed OnThe date and time when the deployment was completed
Compute SizeThe compute resources allocated for running the custom code
DescriptionA summary of what the deployed code does
Deployed ByThe user or process that performed the deployment
Deployment StatusThe current status of the deployment (for example, Deployed)
Code TypeWhether the code is deployed as a Script or Function

The Run History tab displays detailed execution history and performance metrics for your custom code runs. This tab provides comprehensive insights into how your deployed code has performed over time.

The Run History table shows execution details.

FieldDescription
Submitted DateThe date and time when the execution was submitted (clickable link to view execution details)
Called ByThe process that initiated the execution (for example, Batch Transform)
Run StatusThe current status of the execution:
  • Running—Execution is currently in progress (indicated by a loading icon).
  • Success—Execution completed successfully.
  • Failure—Execution failed.
Rows ReadThe number of data rows processed during execution
Rows WrittenThe number of data rows written during execution

When you click the Submitted Date, a Run Summary dialog displays detailed information about that specific execution.

The Run Summary dialog shows the following information about an execution:

FieldDescription
Run StatusThe status of the execution (for example, Success)
RuntimeThe duration of the execution
Rows ReadThe number of data rows processed during execution
Rows WrittenThe number of data rows written during execution
Completed OnThe date and time when the execution completed
Deployed ToThe feature where the custom code is deployed (for example, Batch Transform)
Called ByThe process that initiated the execution (for example, Batch Transform)