---
sourceDocument: Australia Enterprise Architecture
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-portfolio-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Enterprise Architecture

ft:clusterId :

    - appportman

bundleId :

    - appportman

workflow :

    - Technology


---

# Restart the Populate TLM Discovered Technologies and Lifecycles job

# Restart the Populate TLM Discovered Technologies and Lifecycles job {#ariaid-title1}

Release version: Australia  
Updated July 17, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
You can restart the Populate TPM Discovered Technologies and Lifecycles job if it encounters any interruptions or failures.

## Before you begin

Role required: admin

## About this task

Important:  
Technology Lifecycle Management (TLM) was previously known as Technology Portfolio Management (TPM). TPM and TLM refer to the same feature. Table names and scheduled job names continue to use TPM and haven't been renamed.

Whether your instance displays TPM or TLM also depends on your application versions. TLM labels appear only when both the Enterprise Architecture Workspace application (version 9.2.1 or later) and the Technology Lifecycle Management plugin, sn_apm_tpm (version 1.11.0 or later), are installed. If either application is on an earlier version, the interface continues to show TPM.

The restart feature enables you to resume the Populate TPM Discovered Technologies and Lifecycles job from where it stopped. This ensures that the data population process is completed without having to start the
job from the beginning. The job discovers technologies from CMDB and Service Mapping relationships and then populates lifecycle records in the same run. Because both phases run as part of the same job, restarting it resumes
both discovery and lifecycle population from the last processed record.

The Restart button is set to active on the TLM Discovered Technology Run Log page after one hour with no update to the run log. You can determine
whether the job faced any interruption or whether it failed by analyzing the Records Processed field value. If the count of TLM discovered technologies in the system stops increasing while the job is running, the job may have stalled or failed.

## Procedure

1. Navigate to WorkspacesEnterprise Architecture Workspace.
2. Open the Setup page by selecting the Setup icon ![]().
3. Select the expand row icon (![]()) next to Logs.
4. Select the relevant TLM log for the Populate TPM Discovered Technologies and Lifecycles job you are restarting.
5. Select Restart.
{#eaw-restart-tpm-scheduled-job__steps_cmj_1cb_xkc}
**Related concepts**   

* [Exploring Technology Lifecycle Management (TLM) in Enterprise Architecture Workspace](https://www.servicenow.com/docs/BGLPRnuND_K7lEKsDt_4xQ "Technology Lifecycle Management helps Enterprise Architects to track technology life-cycle risks and technology life-cycle exceptions. Enterprise Architects can evaluate all their business applications and application services by accessing the discovered technologies and auditing information in the Enterprise Architecture Workspace.")  
**Related tasks**   

* [Update TLM data for a business application or application service](https://www.servicenow.com/docs/6M29SFzEFz74U0QOnGKq9g "Manually update the Technology Lifecycle Management (TLM) lifecycle data for software and hardware models in your business applications and application services.")
* [View TLM logs](https://www.servicenow.com/docs/TTymR6b~FRHp0fZ49DfMSw "Track the progress of Technology Lifecycle Management (TLM) analysis by examining the TPM Discovered Technology Run Logs [sn_apm_tpm_discovered_technology_run_log] table. Each time the analysis is run, an entry is added to this table.")

*[\>]: and then