Asset – Create Asset Delayed Sync: Scheduled Job Run Frequency - Support and Troubleshooting

Asset – Create Asset Delayed Sync: Scheduled Job Run Frequency .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; } :root { /* ── ServiceNow Brand Colors ── */ --infinite-blue: #032D42; /* Primary — dominant */ --wasabi-green: #63DF4E; /* Accent — use sparingly */ --bright-blue: #52B8FF; /* Supplementary */ --bright-indigo: #7661FF; /* Supplementary */ --bright-purple: #BF71F2; /* Supplementary */ /* ── Derived tokens ── */ --header-bg: var(--infinite-blue); --accent: var(--wasabi-green); --accent-light: #e8fce4; /* Wasabi tint for backgrounds */ --border: #d0dbe0; --text-primary: #0d1f2b; --text-secondary: #3d5a6a; --bg-page: #f2f5f7; --bg-card: #ffffff; --warn-bg: #fff4e0; --warn-border: #e6a817; --note-bg: #e6f4ff; /* Bright Blue tint */ --note-border: var(--bright-blue); --tag-bg: #e8fce4; /* Wasabi tint */ --tag-color: #032D42; --radius: 6px; } body { font-family: 'Lato', sans-serif; font-size: 15px; line-height: 1.7; color: var(--text-primary); background: var(--bg-page); padding: 40px 20px 80px; } .kb-wrapper { max-width: 860px; margin: 0 auto; } /* ── Header bar ── */ .kb-header { background: var(--header-bg); border-radius: var(--radius) var(--radius) 0 0; padding: 28px 36px 24px; color: #fff; } .kb-meta-row { display: flex; flex-wrap: wrap; gap: 8px; margin-bottom: 14px; } .kb-tag { background: rgba(99,223,78,0.18); color: #c8fbc0; font-size: 11.5px; font-weight: 700; letter-spacing: .06em; text-transform: uppercase; padding: 3px 10px; border-radius: 20px; } .kb-title { font-size: 22px; font-weight: 900; line-height: 1.3; color: #ffffff; margin-bottom: 6px; } .kb-subtitle { font-size: 13px; font-weight: 300; color: #82b8d4; letter-spacing: .01em; } /* ── Body card ── */ .kb-body { background: var(--bg-card); border: 1px solid var(--border); border-top: none; border-radius: 0 0 var(--radius) var(--radius); padding: 36px 36px 40px; } /* ── Section headings ── */ .section { margin-bottom: 34px; } .section:last-child { margin-bottom: 0; } .section-label { display: inline-block; font-size: 10px; font-weight: 900; letter-spacing: .12em; text-transform: uppercase; color: var(--accent); margin-bottom: 4px; } h2.section-title { font-size: 16px; font-weight: 900; color: var(--infinite-blue); margin-bottom: 14px; padding-bottom: 8px; border-bottom: 2px solid var(--accent-light); } /* ── Paragraphs & lists ── */ p { margin-bottom: 12px; color: var(--text-primary); } p:last-child { margin-bottom: 0; } ul, ol { padding-left: 22px; margin-bottom: 12px; } li { margin-bottom: 6px; } li:last-child { margin-bottom: 0; } /* ── Inline code ── */ code { font-family: 'Courier New', Courier, monospace; font-size: 13px; background: #e6f0f5; color: #032D42; padding: 1px 6px; border-radius: 3px; border: 1px solid #b8cfd8; } /* ── Callout boxes ── */ .callout { border-left: 4px solid var(--note-border); background: var(--note-bg); border-radius: 0 var(--radius) var(--radius) 0; padding: 13px 16px; margin: 16px 0; font-size: 14px; } .callout.warn { border-left-color: var(--warn-border); background: var(--warn-bg); } .callout strong { display: block; margin-bottom: 4px; font-weight: 700; } /* ── Table ── */ .impact-table { width: 100%; border-collapse: collapse; margin: 16px 0; font-size: 14px; } .impact-table thead tr { background: var(--infinite-blue); color: #fff; } .impact-table thead th { padding: 10px 14px; text-align: left; font-weight: 700; letter-spacing: .02em; } .impact-table tbody tr:nth-child(even) { background: var(--accent-light); } .impact-table tbody td { padding: 10px 14px; border-bottom: 1px solid var(--border); vertical-align: top; } /* ── Ordered steps ── */ .steps-list { list-style: none; padding-left: 0; counter-reset: steps; } .steps-list li { counter-increment: steps; display: flex; gap: 14px; align-items: flex-start; margin-bottom: 14px; } .steps-list li::before { content: counter(steps); flex-shrink: 0; width: 26px; height: 26px; background: var(--infinite-blue); color: var(--wasabi-green); border-radius: 50%; font-size: 12px; font-weight: 900; display: flex; align-items: center; justify-content: center; margin-top: 2px; } /* ── Related section chips ── */ .related-list { list-style: none; padding-left: 0; display: flex; flex-direction: column; gap: 8px; } .related-list li { background: var(--tag-bg); color: var(--tag-color); border: 1px solid #a8dfa0; border-radius: var(--radius); padding: 8px 14px; font-size: 13.5px; font-weight: 700; margin-bottom: 0; } .related-list li span { font-weight: 400; color: var(--text-secondary); margin-left: 6px; } /* ── Footer ── */ .kb-footer { margin-top: 20px; font-size: 12px; color: #6a8a9a; text-align: center; line-height: 1.6; } /* ── Divider ── */ hr.section-divider { border: none; border-top: 1px solid var(--border); margin: 30px 0; }

Asset – Create Asset Delayed Sync: Scheduled Job Run Frequency Issue / Question A customer is requesting to increase the run frequency of the Asset – Create asset delayed sync scheduled job from its default interval of 15 minutes to a shorter interval. This article explains what the job does, why the 15-minute default exists, and the performance implications of increasing the frequency.

Symptoms Asset records are not created immediately after a CI is inserted into the CMDB. A delay of up to 15 minutes is observed between CI creation and the corresponding asset record appearing in the system. Pending asset creation records accumulate in the Asset Creation Queue between scheduled job runs. Users or downstream processes that depend on asset availability encounter records that are not yet present. Facts How the Job Works

The system property glide.create_alm_asset.async controls whether assets are created immediately when a CI is inserted, or asynchronously via a queue:

false (default prior to Washington DC) — Asset is created immediately upon CI insert. true — A queue record is written to the Asset Creation Queue. The Asset – Create asset delayed sync scheduled job processes this queue every 15 minutes and creates the corresponding asset records. Monitoring Job status can be monitored in the asset_job_log table. Assets waiting to be created or in an error state can be viewed at Asset > Administration > Asset Creation Queue . Why Is the Default 15 Minutes?

ServiceNow does not publicly document a specific engineering rationale for the 15-minute default. It is, however, an intentional design choice that balances two competing concerns:

Throughput — Batching CI inserts into a queue allows large Discovery runs to complete faster, eliminating the overhead of per-CI asset creation. System load — A 15-minute interval ensures the job runs infrequently enough to avoid constant background thread contention on the scheduler. Cause When glide.create_alm_asset.async is set to true , the system deliberately defers asset creation to a batch process. The 15-minute run interval is the configured schedule for that batch job. Any perceived delay in asset availability is a direct result of this asynchronous design — assets are not created until the next scheduled job execution processes the queue.

Solution Impact of Increasing the Run Frequency

Changing the interval to a shorter duration causes the job to run more frequently. The actual performance impact depends heavily on instance size and queue volume.

Potential Risks Increased scheduler load — More frequent executions consume more background worker threads, competing with other scheduled jobs and system processes. Mid-queue-flush overlap — On high-volume instances, a shorter interval may trigger a new job run before the previous one finishes — particularly during or after large Discovery imports. Diminishing returns at very short intervals — At very short intervals, behavior approximates setting glide.create_alm_asset.async = false , but without the cleaner built-in handling of synchronous asset creation. Low vs. High Volume Environments

Environment Expected Impact Low volume Small queue between runs Negligible performance impact. Increasing frequency is generally safe. High volume Large Discovery imports, many CIs Higher risk. Job overlap is possible. Monitor closely after any change. Recommended Steps

ServiceNow does not officially recommend changing the default 15-minute interval. Before making any change, follow these steps:

Review the Asset Creation Queue. Navigate to Asset > Administration > Asset Creation Queue . Check how many records are typically queued between runs. A consistently small queue indicates a shorter interval carries low risk. Test in a non-production environment first. Validate the new interval in a sub-production instance during a representative Discovery run before applying the change to production. Adjust the scheduled job interval. Navigate to System Scheduler > Scheduled Jobs and locate Asset – Create asset delayed sync . Modify the run interval to the desired frequency. Monitor the Asset Job Log after the change. Review the asset_job_log table to confirm jobs are completing cleanly, not stacking, and not overlapping between runs. Consider setting glide.create_alm_asset.async to false . If the goal is to eliminate the delay between CI creation and asset availability entirely, immediate asset creation may be a cleaner solution — provided the instance is not processing very large Discovery batches where queuing provides a performance benefit. Note Any modification to scheduled job intervals or system properties is a custom configuration change. Validate all changes through your organization's standard change management process. ServiceNow Professional Services can assist with high-volume or complex implementations. Related References glide.create_alm_asset.async — System property controlling synchronous vs. asynchronous asset creation asset_job_log — Table for monitoring Asset – Create asset delayed sync job runs Asset > Administration > Asset Creation Queue — View queued and errored asset creation records ServiceNow Docs: Work with Asset and CI — latest release documentation