Troubleshooting ServiceNow Software Asset Management Looker integration: Complete Troubleshooting GUIDE; subscriptions, user roles, last login or reclaim not workingSummary :root { color-scheme: light; --blue:#005baa; --ink:#172033; --muted:#5b6678; --line:#d6dee8; --surface:#fff; --page:#f3f6fa; --red:#b42318; --amber:#9a6700; --green:#087443; } * { box-sizing:border-box; } html { scroll-behavior:smooth; } body { margin:0; padding:24px; background:var(--page); color:var(--ink); font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif; line-height:1.55; } .kb-page { max-width:920px; margin:0 auto; } .kb-hero { background:var(--blue); color:#fff; padding:28px 32px; border-radius:10px; margin-bottom:24px; } .kb-eyebrow { margin:0 0 6px; font-size:11px; letter-spacing:1px; opacity:.78; text-transform:uppercase; } .kb-hero h1 { margin:0 0 7px; font-size:clamp(22px,4vw,30px); line-height:1.15; } .kb-lede { margin:0; font-size:14px; opacity:.9; } .kb-badges { display:flex; flex-wrap:wrap; gap:8px; margin-top:16px; } .kb-badge { padding:3px 11px; border-radius:12px; background:rgba(255,255,255,.18); font-size:12px; } .kb-toc,.kb-panel { background:var(--surface); border:1px solid var(--line); border-radius:8px; } .kb-toc { padding:18px 24px; margin-bottom:24px; } .kb-toc-title { margin:0 0 8px; color:#374151; font-size:13px; font-weight:700; letter-spacing:.5px; text-transform:uppercase; } .kb-toc ol { margin:0; padding-left:22px; line-height:2; } .kb-toc a { color:var(--blue); text-decoration:none; } .kb-section { margin-bottom:28px; scroll-margin-top:16px; } .kb-section-title { margin:0; padding:12px 20px; border-radius:8px 8px 0 0; background:var(--blue); color:#fff; font-size:16px; } .kb-panel { padding:20px 22px; border-top:0; border-radius:0 0 8px 8px; } .kb-panel p:first-child { margin-top:0; } .kb-panel p:last-child { margin-bottom:0; } .kb-callout { margin:0 0 18px; padding:13px 16px; border-left:5px solid var(--blue); border-radius:0 7px 7px 0; background:#eef5fc; } .kb-callout.critical { border-color:var(--red); background:#fff1f0; color:#7a271a; } .kb-callout.warning { border-color:var(--amber); background:#fff8e7; color:#6b4d00; } .kb-callout.success { border-color:var(--green); background:#ecfdf3; color:#05603a; } .kb-table-wrap { overflow-x:auto; margin:16px 0; } table { width:100%; border-collapse:collapse; font-size:13px; } th { padding:9px 12px; background:#31506d; color:#fff; text-align:left; } td { padding:9px 12px; border-bottom:1px solid #e5e7eb; vertical-align:top; } tr:nth-child(even) td { background:#f8fafc; } code { padding:1px 4px; border-radius:3px; background:#f1f3f5; font-family:ui-monospace,SFMono-Regular,Menlo,monospace; font-size:.92em; overflow-wrap:anywhere; } pre { overflow:auto; padding:14px; border-radius:6px; background:#111827; color:#f9fafb; } details { margin:0 0 12px; border:1px solid #bfdbfe; border-radius:6px; overflow:hidden; } summary { cursor:pointer; padding:12px 16px; background:#eff6ff; color:#1e3a5f; font-weight:700; } details > div { padding:16px; background:#fff; } .kb-footer { padding:16px 20px; color:var(--muted); font-size:12px; background:#f8fafc; border:1px solid var(--line); border-radius:8px; } @media (max-width:640px) { body { padding:12px; } .kb-hero { padding:22px 20px; } .kb-panel { padding:16px; } .kb-section-title { padding:11px 16px; } th,td { min-width:140px; } } .kb-hero { padding:24px 28px; } .kb-toc ol { display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:2px 26px;line-height:1.7; } .kb-toc li { padding:3px 0; } h3 { color:#183653;line-height:1.3; } a { color:#005baa;overflow-wrap:anywhere; } th,td { overflow-wrap:anywhere; } pre code { padding:0;background:transparent;color:inherit;overflow-wrap:normal; } code.kb-err { color:#c62828;font-weight:700;background:#fdecea; } .kb-err-list { display:flex;flex-wrap:wrap;gap:6px;margin-top:8px;font-weight:400; } .kb-err-chip { display:inline-block;max-width:100%;padding:2px 8px;border-radius:4px;background:#fdecea;border:1px solid #f5c2c0;color:#c62828; font-family:ui-monospace,SFMono-Regular,Menlo,monospace;font-size:12px;font-weight:700;line-height:1.45;overflow-wrap:anywhere; } .kb-sum-title { font-weight:700; } .branch-index { margin:18px 0 20px;padding:14px 18px;background:#f8fafc;border:1px solid var(--line);border-radius:8px; } .branch-index ol { list-style:none;margin:0;padding:0;display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:6px 28px; } .branch-index li { font-size:14px;line-height:1.45;padding:4px 0; } .kb-section-title + .kb-panel { margin-top:0; } details > div p { margin:0 0 14px; } details > div p:last-child { margin-bottom:0; } @media(max-width:640px) { .kb-toc ol,.branch-index ol { grid-template-columns:1fr; } .kb-hero {padding:20px;} } @media print { body {padding:0;background:#fff;} .kb-toc,.branch-index {display:none;} } .flow { margin:4px 0 26px;padding:18px;border-radius:12px;background:linear-gradient(135deg,#f8fafc,#eef2ff);border:1px solid var(--line); } .flow-intro { display:flex;flex-wrap:wrap;justify-content:space-between;gap:10px;font-size:13px;color:#475569;margin-bottom:14px; } .flow-legend { display:flex;flex-wrap:wrap;gap:6px; } .flow-key { padding:2px 9px;border-radius:10px;background:var(--b);color:var(--c);font-weight:700;font-size:11px;border:1px solid var(--c); } .flow-lane { margin-top:14px; } .flow-lane-head { display:flex;align-items:center;gap:10px;margin-bottom:8px;color:#0f172a; } .flow-lane-head span { font-size:11px;padding:2px 8px;border-radius:10px;background:#0f172a;color:#fff;text-transform:uppercase;letter-spacing:.05em; } .flow-track { display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:16px 30px; } .flow-node { position:relative;display:flex;flex-direction:column;gap:3px;padding:12px 10px 10px 12px;border-radius:10px; background:var(--b);border:2px solid var(--c);color:#1e293b;text-decoration:none;box-shadow:0 1px 2px rgba(15,23,42,.06); transition:transform .2s ease,box-shadow .2s ease;animation:flowPulse 4.4s ease-in-out infinite;animation-delay:var(--d); } .flow-node::after { content:"";position:absolute;top:50%;right:-27px;width:22px;height:4px;margin-top:-2px;border-radius:2px; background:repeating-linear-gradient(90deg,var(--c) 0 6px,transparent 6px 10px);background-size:20px 4px;animation:flowDash .8s linear infinite;opacity:.7; } .flow-node:nth-child(4n)::after,.flow-node:last-child::after { display:none; } .flow-node:hover,.flow-node:focus { transform:translateY(-3px);box-shadow:0 8px 20px rgba(15,23,42,.18);outline:none;z-index:5; } .flow-node:focus-visible { outline:3px solid var(--c);outline-offset:2px; } .flow-num { position:absolute;top:-9px;left:-9px;width:22px;height:22px;border-radius:50%;background:var(--c);color:#fff;font-size:12px;font-weight:700; display:flex;align-items:center;justify-content:center;box-shadow:0 0 0 2px #fff; } .flow-title { font-weight:700;color:var(--c);font-size:13.5px;line-height:1.25; } .flow-what { font-size:12px;line-height:1.35;color:#334155;overflow-wrap:anywhere; } .flow-tip { position:absolute;left:50%;top:calc(100% + 8px);transform:translateX(-50%) translateY(-4px);width:210px;padding:10px 12px;border-radius:8px; background:#0f172a;color:#f8fafc;font-size:12px;line-height:1.4;opacity:0;pointer-events:none;transition:opacity .18s ease,transform .18s ease;z-index:10; } .flow-tip::before { content:"";position:absolute;top:-6px;left:50%;margin-left:-6px;border:6px solid transparent;border-top:0;border-bottom-color:#0f172a; } .flow-tip em { display:block;margin-top:6px;font-style:normal;color:#93c5fd;font-weight:700; } .flow-node:hover .flow-tip,.flow-node:focus .flow-tip { opacity:1;transform:translateX(-50%) translateY(0); } .tri { margin:14px 0 20px;padding:16px;border-radius:12px;background:#0f172a;color:#e2e8f0; } .tri-head { font-size:12px;text-transform:uppercase;letter-spacing:.08em;color:#93c5fd;font-weight:700;margin-bottom:12px; } .tri-row { display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:12px 26px; } .tri-step { position:relative;display:flex;flex-direction:column;gap:4px;padding:12px;border-radius:10px;background:#1e293b;border:1px solid #334155; animation:triGlow 4.2s ease-in-out infinite;animation-delay:var(--d); } .tri-step::after { content:"";position:absolute;top:50%;right:-22px;width:16px;height:3px;background:repeating-linear-gradient(90deg,#60a5fa 0 5px,transparent 5px 8px); background-size:16px 3px;animation:flowDash .7s linear infinite; } .tri-step:last-child::after { display:none; } .tri-step strong { color:#f8fafc;font-size:14px; } .tri-where { font-size:12px;color:#93c5fd; } .tri-tells { font-size:12px;color:#cbd5e1;line-height:1.35; } .tri-num { position:absolute;top:-9px;left:-9px;width:22px;height:22px;border-radius:50%;background:#2563eb;color:#fff;font-size:12px;font-weight:700;display:flex;align-items:center;justify-content:center; } @keyframes triGlow { 0%,100% { border-color:#334155;box-shadow:none; } 10% { border-color:#60a5fa;box-shadow:0 0 0 3px rgba(96,165,250,.35); } 22% { border-color:#334155;box-shadow:none; } } .tri-row.tri-5 { grid-template-columns:repeat(5,minmax(0,1fr)); } @media (max-width:820px) { .tri-row,.tri-row.tri-5 { grid-template-columns:repeat(2,minmax(0,1fr)); } .tri-step:nth-child(2n)::after { display:none; } } @media (max-width:520px) { .tri-row { grid-template-columns:1fr; } .tri-step::after { display:none; } } @media (prefers-reduced-motion: reduce) { .tri-step,.tri-step::after { animation:none; } } @keyframes flowPulse { 0%,100% { box-shadow:0 1px 2px rgba(15,23,42,.06); } 8% { box-shadow:0 0 0 4px var(--b),0 0 0 6px var(--c),0 6px 18px rgba(15,23,42,.2); } 18% { box-shadow:0 1px 2px rgba(15,23,42,.06); } } @keyframes flowDash { to { background-position:20px 20px; } } @media (prefers-reduced-motion: reduce) { .flow-node,.flow-node::after { animation:none; } } @media (max-width:820px) { .flow-track { grid-template-columns:repeat(2,minmax(0,1fr)); } .flow-node:nth-child(4n)::after { display:block; } .flow-node:nth-child(2n)::after { display:none; } } @media (max-width:520px) { .flow-track { grid-template-columns:1fr;gap:24px; } .flow-node::after,.flow-node:nth-child(4n)::after,.flow-node:nth-child(2n)::after { display:block;top:auto;bottom:-22px;right:auto;left:50%;width:4px;height:18px;margin:0 0 0 -2px; background:repeating-linear-gradient(180deg,var(--c) 0 6px,transparent 6px 10px);background-size:4px 20px; } .flow-node:last-child::after { display:none; } .flow-tip { position:static;transform:none;width:auto;margin-top:6px;display:none;opacity:1; } .flow-node:focus .flow-tip,.flow-node:hover .flow-tip { display:block;transform:none; } } @media print { .flow-node,.flow-node::after { animation:none; } .flow-tip { display:none; } } Software Asset Management - Knowledge Article Troubleshooting ServiceNow SAM Looker integration: subscriptions, user roles, last login or reclaim not working Find the failing stage, correct its cause, and verify complete recovery. Contents Scope and applicabilityImplementation checklistSymptoms and expected behaviorExecution path and evidence correlationDetailed troubleshooting branchesCause-specific correction and controlled recoveryVerification criteria and recovery evidenceEscalation evidence to collectReferences, processing rules and known limitationsServiceNow Otto / Now Assist troubleshooting 1. Scope and applicability This article covers the Looker direct integration profile (label Looker Subscription, profile type looker_subscription). It is a subflow-based integration delivered by the Looker Spoke (selected as an optional feature when SaaS License Management is installed). Two subflows run: Looker Download Subscriptions and Looker Reclaim Subscription. The download subflow also applies the last login, so there is no separate activity subflow and no separate activity job is documented. One connection. A single Connection & Credential (alias sn_looker_spoke.Looker) signs in to one Looker instance with the Client ID and Client secret of an API3 key created for a Looker administrator account. The Connection URL is the Looker base URL, in the form https://<instance_name>.looker.com. What it counts. The download first reads all roles defined in Looker, then reads every user, and works out each user's license type from the roles assigned to that user (for example Developer or Admin, Standard creator, Viewer). Each user becomes one subscription. How a given license type maps to a software model is shown in the generated models; check them against your Looker licenses (branch J). What last activity means. Last activity is the user's last Looker login, applied during the download as a login event. Activity inside dashboards or explores is not read. What reclaim does. Reclaim calls the spoke action Delete User, which deletes the specified user and the user's associated records from Looker. The effect on content owned by that user is not stated in the sources, so read branches O and P before approving candidates. It does not cover Looker Studio, Looker (original) deployments that your instance cannot reach, or the Looker data catalog collector. Applies to: SAM Professional with the Software Asset Management - SaaS License Management (sn_sam_saas_int) Store application and the Looker Spoke (which needs IntegrationHub). A spoke version before 1.0.1 failed on paging; older SaaS License Management releases mapped some users to a lower license type or failed on unknown roles (branches H, J and G). Keep both current and compare with the release documentation before applying a version-specific conclusion. 2. Implementation checklist CheckWhere and what to inspectReady conditionApplication and spokeApplication Manager: SaaS License Management and the Looker Spoke optional featureInstalled and current; IntegrationHub presentRoles (ServiceNow)User creating the profilesam_integratorLooker roleThe Looker administrator who creates the API3 keyAdminLooker API3 keyLooker > Admin (gear icon) > Users > open the admin user > Edit API3 Keys > New API3 KeyClient ID and Client secret copiedProfileSoftware Asset Workspace > License operations > User subscriptions > Direct integration profiles > New > Looker > ContinueDisplay name; profile type Looker Subscription; subflows Looker Download Subscriptions and Looker Reclaim SubscriptionCheckboxesProfileDownload subscriptions on (cannot be cleared); Reclaim subscriptions on by defaultConnectionProfile > Connection & Credential (sn_looker_spoke.Looker) > Create New Connection & CredentialConnection name, Connection URL https://<instance_name>.looker.com, OAuth Client ID, OAuth Client Secret, OAuth Redirect URL https://<your instance>/oauth_redirect.doTokenCreate Connection and Credential dialogCreate and Get OAuth Token selectedValidation and publishProfile > Validate Connection then PublishSucceeds; the job is created after validationJobProfile > Scheduled JobsSAM - Refresh <name> Subscriptions (daily); active, no duplicatesEntitlementsSoftware models for LookerEntitlements created, then reconciliation runUserssys_user email versus Looker emailResolvable, or user resolution rules exist Looker permissions and roles ProcessLooker role or permissionScopesDownload subscriptionsA user with the see_users permissionNoneLast loginA user with the see_users permissionNoneReclaim subscriptionsAdminNone The API3 key belongs to one Looker user, and the integration acts as that user. The setup steps in the documentation use an administrator, which covers all three processes. A user with only see_users can download but cannot delete users. What happens when a setting is missing or wrong Setting, field or propertyIf it is missing or wrongTypical symptomLooker Spoke optional feature not installedNo Looker profile type or subflowsOption missing when creating the profile (A)Wrong Connection URL (not your Looker base URL)Requests go to the wrong hostConnection validation is not successful. Please check connections and credentials and try again.Wrong Client ID or Client secret, or API3 key deletedSign-in refusedGeneric validation message; HTTP 401 in outbound HTTP logsLooker user behind the key lacks see_usersUser list refusedValidation fails or the download returns 403Looker user behind the key is not an AdminDelete User refusedReclaim fails with an authorization errorCreate and Get OAuth Token not completedNo token storedValidation fails immediatelyReclaim subscriptions clearedCandidates created, reclaim never runsThe reclamation of user subscriptions will not be successful because the Reclaim subscription checkbox isn't selected on the integration profile.Profile edited after publishStatus returns to DraftJobs stop until validated and published againRole list incomplete (a user holds a role the role lookup did not return)Older releases failed the whole downloadCannot read property "name" from undefined (G)Entitlements missingNothing to reconcile againstCompliance shows nothingNo matching sys_userSubscription user stays emptyReconciliation consumes no rightDebug properties left onExtra loggingSlow instance after troubleshooting 3. Symptoms and expected behavior SymptomFirst branchHealthy evidence to seekLooker option, spoke or job missingALooker profile type available, job listedCannot create the connection or publishBStatus Published with its jobValidate Connection failsCValidation successfulAPI3 key, Looker role or permission problemsDSign-in succeeds, user list returnedAuthentication fails after a whileEFresh token, job completingWrong Looker instance or URLFIntended instance returns usersJob or subflow failedGCompleted row in the job log and flow executionCounts differ from LookerHCounts match Looker usersSeveral Looker instancesIOne profile and connection per instanceModel, license type or entitlement problemsJLooker model on every subscriptionUser empty or wrongKIntended sys_user linkedLast activity blank or staleLRecent login for an active userLast activity missing for a whole group of usersMDownload completes without errorsNo or wrong reclamation candidatesNCandidates only for truly inactive usersReclaim failsOUser removed in LookerAfter reclaim: content, stuck candidatesPCandidate closedRate limits, timeouts, pagingQNormal run durationProblems after clone, upgrade or repairRValidated profile, valid credentials A healthy download creates one subscription per Looker user, with the license type taken from the user's roles and the last login as last activity. Subscriptions for users who no longer appear are removed on the next run. 4. Execution path and evidence correlation Hover or tap a step to see what breaks there; click it to open the matching branch.SetupConnectionCollectionMatchingWriteDownstream Setup and downloaddaily 1API3 keyLooker admin creates a key; Client ID and secretBreaks here: Key deleted; account without see_usersOpen branch D →2Connection URLhttps://<instance_name>.looker.com; Create and Get OAuth TokenBreaks here: Wrong base URL; token not createdOpen branch C →3Validate and publishDownload calls only; not reclaimBreaks here: Generic validation messageOpen branch C →4Subscriptions jobSAM - Refresh <name> SubscriptionsBreaks here: Failed run; role lookup errorOpen branch G →5Look up RolesAll roles with license typeBreaks here: Role not returned for a userOpen branch G →6Look up Users StreamPaged user list with role IDsBreaks here: HTTP 400 paging; empty resultOpen branch Q →7License type and userType from roles; email to sys_userBreaks here: Lower type; empty userOpen branch J →8Upsert and last loginSubscription per user; Update Login Event ActivityBreaks here: Blank or stale activityOpen branch L → Candidates and reclaimafter download 1Reclamation rule60-day rule created onceBreaks here: Wrong candidatesOpen branch N →2Candidate approvalReview before approvingBreaks here: Blank activity proposes active usersOpen branch N →3Delete UserDeletes user and associated recordsBreaks here: 403 not Admin; 404 goneOpen branch O →4Content and recoveryNot reversible from ServiceNowBreaks here: Content lost with the userOpen branch P →5After clone or upgradeRecreate key and tokenBreaks here: Stale tokens, missing optionsOpen branch R → Subscription and last-login path Subscriptions job (daily) → Looker Download Subscriptions subflow → Look up Roles (all roles, license type per role) → Look up Users Stream (paged) → license type and role names built per user → upsert subscription per user → Update Login Event Activity (last login) → delete users not returned → reclamation rule (60 days) → user resolution Reclaim path Candidate approved → Looker Reclaim Subscription subflow → Delete User for the Looker user ID → candidate completes StageRecord or source to inspectBehaviorJobProfile > Scheduled Jobs and Scheduled Job ResultsOne daily job: SAM - Refresh <name> SubscriptionsFlow runFlow Designer > Operations > ExecutionsDownload subflow run with the failing step and its errorRolesLook up Roles outputRole ID, role name and license type for every role defined in LookerUsersLook up Users Stream outputPaged; each user has ID, email, role IDs and a disabled flagUpsertsamp_sw_subscriptionOne row per userLast activitySubscriptionLast login only; moves forward onlyReclaimDelete User actionUser and associated records removed in Looker Correlate one execution before deciding a cause Record the job, profile, start and end in UTC, and the application and spoke versions.Open the profile's Scheduled Job Results and sam_saas_job_log; read the message.Open Flow Designer > Operations > Executions and find the subflow run for the same window; open the failing step. Scripts that build the user type and role names run as steps of the download subflow, so a script error shows here with the line text.Open System Logs > All and look for Datastream error: for the same window (a failed validation shows only a generic message in the form; the detail is in the log).Open System Logs > Outbound HTTP Requests and filter for your Looker host to see the status code of each call (a 400 on the users call points to paging, branch Q).For deeper tracing, set com.snc.process_flow.reporting.level to All and, if needed, glide.outbound_http_log.override to true with glide.outbound_http_log.override.level set to all; rerun once, then set them back. There are no Looker-specific debug properties. 5. Detailed troubleshooting branches Each branch lists the symptoms with the exact text the integration writes, where to look, each cause with its fix, and how to confirm recovery. Identifiers shown as <id>, <name> or <instance_name> are placeholders; keep the real values private. Start every investigation here 1Job resultProfile > Scheduled Job ResultsStatus and message of the run 2System logFlow Designer > Operations > Executions; sam_saas_job_logFailing subflow action and its error 3Outbound HTTPSystem Logs > All: Datastream errorThe real reason behind the generic validation message 4Pick a branchMatch the message below401 → D/E, 403 → D/O, 404 → F, 400 → Q, role name error → G Start every investigation the same way. (1) The profile's Scheduled Job Results. (2) Flow Designer > Operations > Executions for the subflow. (3) System Logs > All for Datastream error: and the Looker error text. Read the message, not only the status. A. Looker option, spoke or job is missingB. The connection cannot be created, or the profile cannot be publishedC. Validate Connection failsD. API3 key, Looker role or permission problemsE. Authentication fails after a whileF. Wrong Looker instance or URLG. The refresh job or subflow failsH. Subscription counts differ from LookerI. Several Looker instancesJ. Model, license type or entitlement problemsK. Subscription user is empty or wrongL. Last activity is blank or staleM. Last activity missing for a whole group of usersN. No reclamation candidates, or wrong onesO. Reclaim failsP. After reclaim: content, access and stuck candidatesQ. Rate limits, timeouts, paging and large instancesR. Problems after a clone, upgrade or repair A. Looker option, spoke or job is missing Symptoms. Looker is not offered when creating a direct integration profile.The sn_looker_spoke.Looker connection alias is not listed.No SAM - Refresh <name> Subscriptions job after publishing. Where to check. Application Manager > SaaS License Management version; the optional feature Looker Spoke; the profile's Scheduled Jobs list. Causes and fixes. Looker Spoke not selected. The Looker Spoke check box must be selected when optional features are chosen for SaaS License Management. Install or update with it selected (IntegrationHub is required).Core UI create option inactive. With Software Asset Workspace installed, create the profile from License operations > User subscriptions > Direct integration profiles > New > Looker.Profile type routing removed after an upgrade. If a job fails after an upgrade because the profile type is not recognized, repair the SaaS License Management plugin so the integration routing rows are restored.Jobs not created. The job is created only after validation succeeds (B). Verify. The profile shows Published with its job. B. The connection cannot be created, or the profile cannot be published Symptoms. You cannot create the connection (missing role).No Publish option, or a published profile is back in Draft.The connection dialog closes without a token. Where to check. The profile form (Status); the Connection & Credential record; the user's roles. Causes and fixes. Role. Creating the profile and connection needs sam_integrator.Connection section not shown. Save the draft first; the Connection & Credential field then appears set to sn_looker_spoke.Looker. Open the record with the preview icon and Open Record, then use Create New Connection & Credential.Token step skipped. Fill in the Client ID, Client Secret and OAuth Redirect URL, then select Create and Get OAuth Token. Saving without it leaves no token.Redirect URL. Use https://<your instance>/oauth_redirect.do with your own ServiceNow instance name.Not validated. The job is created only after Validate Connection succeeds (C).Edited after publish. Changing the connection returns the profile to Draft; validate and publish again.Where Now Assist for SAM is available, use Troubleshoot on the error banner (section 10). Verify. Status Published, with the subscriptions job. C. Validate Connection failsConnection validation is not successful. Please check connections and credentials and try again. Symptoms. Connection validation is not successful. Please check connections and credentials and try again.Validation ends at once without a more specific message. Where to check. System Logs > All for Datastream error:; the credential record; the Connection URL. Causes and fixes. What validation tests. It verifies the Download Subscriptions calls. It does not test reclaim, so a pass does not prove deletion works.Generic message. Any failure of the download call shows the generic message; the real reason is in the system log and in the Outbound HTTP Requests status (401, 403, 404 meanings are in branches D to F).Wrong Connection URL. It must be your Looker base URL, https://<instance_name>.looker.com, with no path. Correct it on the connection.Token missing or stale. Select Create and Get OAuth Token again on the connection.Key values wrong. Copy the Client ID and Client secret again from the API3 key (D).Connection or credential missing. Create the connection, or delete and recreate it if the credential is missing. Verify. Validation successful and the job is created. D. API3 key, Looker role or permission problems Symptoms. HTTP 401 for the sign-in call in the outbound HTTP log.HTTP 403 for the users or roles call, or for deleting a user.Validation passes but reclaim fails. Where to check. Looker Admin > Users > the account that owns the API3 key; the credential record; the outbound HTTP log. Causes and fixes. Create the key correctly. In Looker, open Admin (gear icon) > Users, open the administrator account, select Edit API3 Keys under the Profile tab, then New API3 Key. Copy the Client ID and Client secret at once.Wrong role. The account must have the see_users permission to download and read last login, and must be an Admin to delete users. Use an administrator for all three processes.Key deleted or account disabled. If the Looker account behind the key is disabled, removed or its key is deleted, sign-in fails; create a new key on a current administrator and update the credential.Values copied wrongly. Copy the Client ID and secret again; the secret is shown when the key is created.Instance restrictions. If Looker restricts API access by network, allow the ServiceNow instance or MID Server addresses (this restriction is a Looker setting; the sources do not describe it). Verify. Sign-in succeeds and validation returns Validation successful; a test reclaim of one user succeeds. E. Authentication fails after a while Symptoms. Jobs worked at first and then fail with authentication errors.HTTP 401 in the outbound HTTP log. Where to check. The Connection & Credential record (token and expiry); Looker's API3 keys for the account. Causes and fixes. Key rotated or deleted in Looker. Create a new API3 key and update the credential, then select Create and Get OAuth Token.Administrator left. If the Looker account that owns the key is disabled or deleted, authentication fails; create the key on a current administrator.Token not refreshed. The sources do not state the token lifetime or the refresh behavior. If a failure follows a long idle period, run Create and Get OAuth Token again and rerun the job.Clone. Tokens do not carry across a clone (R). Verify. The job completes and the credential shows a fresh token. F. Wrong Looker instance or URL Symptoms. No users returned; HTTP 404; users from a different Looker instance (for example a test instance). Where to check. The Connection URL; the Looker address in your browser. Causes and fixes. Base URL. Use the same host you use to sign in to Looker, as https://<instance_name>.looker.com.Custom domain. If your Looker is reached through a custom domain, the sources do not describe it; use the host that your API3 key belongs to and test with validation.Several instances. One connection holds one Looker instance (I). Verify. The user list returns the intended instance's users. G. The refresh job or subflow failsCannot read property "name" from undefinedCannot invoke "com.snc.cobject.ComplexObjectCollection.size()" because "outputItems" is nullEncountered an error. Check error log for more information.An instance of '<job>' is already running Symptoms. Scheduled Job Results shows Failed, or the flow execution shows a failed step, with: Cannot read property "name" from undefinedCannot invoke "com.snc.cobject.ComplexObjectCollection.size()" because "outputItems" is nullEncountered an error. Check error log for more information.An instance of '<job>' is already running Where to check. The job result; sam_saas_job_log; Flow Designer executions; System Logs > All. Causes and fixes. Unknown role on a user. Cannot read property "name" from undefined appears when a user holds a role ID that the role lookup did not return (Looker also keeps built-in or legacy roles that do not appear in the role list). The download fails at the step that builds the role names. Update SaaS License Management to the current release, where this case is handled, and rerun. As a workaround, remove the unusual role from the affected Looker user.Empty user result. Cannot invoke ... "outputItems" is null was raised by older releases when the user call returned an empty list (for example an invalid user filter); update the Looker Spoke and the platform.Looker error. Match the text to branches D, E, F or Q.Outdated application or spoke. Update SaaS License Management and the Looker Spoke, then run the job once.Job linked to a removed profile. Delete the orphan job and republish.Two runs at once. Wait for the active run to finish.Failed run. Fix the cause and rerun; deletions already made are not undone. Verify. The next run shows Completed and updated subscriptions. H. Subscription counts differ from Looker Symptoms. Counts are lower or higher than the Looker user list; disabled users appear or are missing; a user shows the wrong license type. Where to check. Looker Admin > Users (roles per user); exclusion rules. Causes and fixes. One subscription per user. Every user returned by the user list becomes a subscription. The sources do not state whether disabled users are skipped; compare a sample of disabled users with the imported list.License type from roles. A user can hold several roles, each built from a permission set and a model set, and a user's license type comes from the highest qualifying permission. A user with several roles combining Viewer, Standard creator and Admin permission sets was mapped to a lower type in older releases; update SaaS License Management.Exclusion rules. Subscription Identifier Exclusion Rule and Subscription User Exclusion Rule silently drop matching rows.Users missing. A failed run keeps old rows but does not add new ones; see G.Another instance. A user belongs to a different Looker instance (F, I). Verify. Counts and license types match Looker's user list. I. Several Looker instances Symptoms. A second Looker instance is not imported; two profiles show the same users. Where to check. Each profile's connection and its Connection URL. Causes and fixes. One profile per instance. A connection holds one Looker base URL; create a profile and a connection for each instance.Child aliases. For several profiles, create child aliases of sn_looker_spoke.Looker, a connection on each child alias, and select it on each profile.Not documented. The sources do not describe other multi-instance behavior; test with one instance first. Verify. Each profile imports only its own instance's users. J. Model, license type or entitlement problems Symptoms. A raw identifier and no software model; entries under Unrecognized Subscription Identifiers; compliance shows nothing; users on the wrong model. Where to check. Profile > Software Models and Unrecognized Subscription Identifiers; entitlements. Causes and fixes. Entitlements missing. Software models and reclamation rules are created automatically and refreshed daily; entitlements are not. Create entitlements for the Looker models and run reconciliation.License type versus model. The integration derives a user type from the user's roles (Developer or Admin, Standard creator, Viewer). Open the generated models and compare them with the license types you bought in Looker. The sources do not list the model names.Wrong type after role changes. Roles are read on each run; after changing roles in Looker, run the job again.Unknown identifier. Open it under Unrecognized Subscription Identifiers, set the correct software model and save.Content out of date. Download current subscription-identifier content. Verify. Subscriptions show the right Looker model and reconciliation produces results. K. Subscription user is empty or wrong Symptoms. Subscriptions with an email but no User; records on the Subscriptions without user page. Where to check. sys_user email versus the Looker email; User resolution rules; sn_itam_samp.user_resolution_exclude_table. Causes and fixes. No match. Align the data or add a user resolution rule (Software Asset Workspace > License operations > User subscription > User resolution rules), then rerun the refresh job.Same email in several user tables. List the extra tables in sn_itam_samp.user_resolution_exclude_table.Manual edits overwritten. The User field is recalculated each run.Looker accounts without an email. Service or API-only accounts may have no email; use an exclusion rule or a rule that matches on another field.Rules created later. An older version filled the user only for new records after a rule was created; update the application. Verify. The subscription shows the intended user. L. Last activity is blank or stale Symptoms. Looker subscriptions have no last activity, or it does not move. Where to check. The subscription's last activity; Looker's last login for the same user; the download job result. Causes and fixes. What it measures. Last activity is the last Looker login applied by the Update Login Event Activity step of the download. A user who has never logged in can show no date.No separate activity job. Last activity is updated only when the subscriptions job completes.Download not healthy. A failed download leaves last activity unchanged (G).Permission. The key's user needs see_users to read login information (D).Date handling. Compare in UTC.Never cleared. Last activity only moves forward. Verify. A user who logged in today shows today's date after the next job run. M. Last activity missing for a whole group of users Symptoms. Many users share the same blank last activity, after a download that shows Completed.The flow execution shows the activity step skipped or with no output. Where to check. The flow execution; the outbound HTTP log for the users call. Causes and fixes. Event storage turned off. If com.snc.samp.disableeventstorage is true, usage events are not stored; last activity should still update, but confirm the property value.Users who never logged in. Newly created Looker accounts have no login yet.Update the spoke. Update the Looker Spoke and rerun.Review early candidates. Candidates created from blank activity may be wrong; review or reject them (N).Not documented. The sources do not state which Looker field provides the login date; if a whole group is blank, compare the Looker user's last login in Looker with the subscription. Verify. The job completes without errors and last activity populates for users who logged in. N. No reclamation candidates, or wrong ones Symptoms. Inactive users get no candidate; active users are proposed for removal. Where to check. The Looker reclamation rule; subscriptions' user and last activity; existing candidates. Causes and fixes. Last activity blank or incomplete. Candidates depend on last login; fix L and M first.Rule configuration. A rule with a 60-day threshold is created automatically, once. Confirm Create reclamation candidate is checked and the threshold is what you want. Do not delete the rule while the profile is active.Users who use only embedded content. Users who see Looker content only through embedded applications may not log in directly and look inactive; review them before reclaiming.User empty. With Notify user on, a candidate without a user goes to Attention Required; fix K.Candidate states. Attention Required, Ready, Awaiting User, Awaiting Approval, Awaiting Revocation, Closed Complete, Closed Skipped, Closed Canceled (cancelled when activity is detected).Do not approve automatically. Reclaim deletes users (O); review candidates first. Verify. A user inactive beyond the threshold receives one candidate; active users do not. O. Reclaim failsThe reclamation of user subscriptions will not be successful because the Reclaim subscription checkbox isn't selected on the integration profile. Symptoms. The reclamation of user subscriptions will not be successful because the Reclaim subscription checkbox isn't selected on the integration profile.An authorization failure (HTTP 403) when deleting the user.HTTP 404 for a user who no longer exists.Candidate in Attention Required or stuck in Awaiting Revocation. Where to check. The candidate's banner; the flow execution of the reclaim subflow; the user in Looker. Causes and fixes. Reclaim not configured. Select Reclaim subscriptions, validate and publish. If the box is cleared, candidates are created but the reclaim subflow is not triggered.Not covered by validation. Validation does not test reclaim; test with one candidate.Role. The Looker user behind the key must be an Admin to delete users (D).Token. The sign-in failed; see D and E.User already removed. HTTP 404 means the user no longer exists in Looker; confirm and close the candidate.Missing user ID. The subscription has no Looker user ID; run the subscriptions job to refresh it. Verify. The user is deleted in Looker, the candidate closes and the subscription is removed on the next download. P. After reclaim: content, access and stuck candidates Symptoms. The user's content or schedules are missing in Looker after reclaim.A user is deleted but the candidate stays open.A user was reclaimed by mistake. Where to check. The user and content in Looker; the candidate's state. Causes and fixes. Delete User removes the user and associated records. The documentation states that the action deletes the user and associated records. The sources do not describe what happens to dashboards, looks or schedules the user owned; move or back up important content in Looker before approving reclaim for its owner.No downgrade. Reclaim deletes; it does not lower the user to a cheaper license type.Candidate stays open. Run the subscriptions job; the candidate is checked again later and closes when the subscription is gone.Wrong user removed. ServiceNow does not reverse a reclaim; recreate the user and licenses in Looker. Verify. The license is freed in Looker and the candidate is Closed Complete. Q. Rate limits, timeouts, paging and large instances Symptoms. HTTP 400 on the users call; HTTP 5xx or throttling in the log; very long runs; counts off by a page. Where to check. The Outbound HTTP Requests log for the users call; the flow execution timing. Causes and fixes. Paging 400. Older spoke versions requested the next page with a decimal value (for example 1000.0 instead of 1000), and Looker refused it with HTTP 400. Update the Looker Spoke to the current version.Limits. The sources document no Looker limit and the retry settings of the spoke were not available; read the error text.Large instances. Run the job off peak and compare counts with Looker after the run.Network. Check the proxy, MID Server or firewall path from the instance to your Looker host. Verify. A complete run without errors and a normal duration. R. Problems after a clone, upgrade or repair Symptoms. Validate or Publish missing after an upgrade; credentials fail after a clone; the profile type is missing; routing errors after an upgrade. Where to check. Installed versions; customizations of SaaS License Management; the credential record; sys_trigger for upgrade fix jobs. Causes and fixes. Form damaged by customization. Check customized files for the profile form, set them to be replaced on upgrade, then repair only SaaS License Management.Profile type routing removed. Repair the SaaS License Management plugin (A3).Credentials after a clone. Re-enter or recreate the Looker credential, select Create and Get OAuth Token and validate on the target instance; do not expect it to carry over. The OAuth Redirect URL must name the target instance.Upgrade fix jobs. They run as scheduled jobs and set profile properties that enable Validate Connection; check sys_trigger and let them finish.Versions out of step. Update SaaS License Management and the Looker Spoke together. Verify. Validation succeeds and the job completes in the target instance. 6. Cause-specific correction and controlled recovery Validation, publish, downloads and reclaim are write operations; reclaim also deletes Looker users. Obtain approval before running them in production. Established causeCorrection ownerControlled recovery and stop conditionApplication, optional feature or spokeServiceNow platform administratorUpdate, validate, publishAPI3 key, role or permissionLooker administrator and integration ownerFix the key or role, validateAuthentication after a whileIntegration ownerRecreate the key and token, confirm a run completesInstance or URLIntegration ownerCorrect the Connection URL, validateRoles and license typesSAM administratorUpdate the application, rerun, compare typesMapping and user resolutionSAM administratorCreate entitlements, add rules, rerunLast activitySAM integration ownerRun after a good download, check logsReclaimSAM process owner and Looker administratorReview candidates, protect content, reclaim one first, confirm in LookerClone, upgrade, repairPlatform ownerRestore out-of-box components, recreate credentials, validate, run once 7. Verification criteria and recovery evidence Verification layerEvidence requiredWhat does not satisfy itConfigurationPublished profile, valid credential and token, Connection URL matchingA Published status after an unvalidated connection changeExecutionCompleted job result and subflow executionA scheduled job that existsCoverageSubscriptions match Looker usersTotals that include accounts you meant to excludeMatchingLooker model and user on every subscriptionRaw identifiers as display namesActivityRecent login for a known active userBlank activity read as inactivityReclaimUser deleted in LookerCandidate closed without the Looker change 8. Escalation evidence to collect Application, Looker Spoke and platform versions; recent upgrades, repairs or clones.Profile status, selected options, the Looker role or permissions of the user behind the API3 key (no keys or secrets).Job name, run time in UTC, job result status and message; the flow execution and failing step; the matching system log lines.The status code of the failing outbound call.Counts of users in Looker and subscriptions in ServiceNow; the roles of one affected user.Steps already taken and results. Never include API keys, secrets, host names or user names in shared evidence. 9. References, processing rules and known limitations Key records Job: SAM - Refresh <name> Subscriptions (daily).Subflows: Looker Download Subscriptions, Looker Reclaim Subscription.Spoke actions: Look up Roles, Look up Users Stream, Update User, Delete User, User Inputs - Dynamic.Connection alias sn_looker_spoke.Looker (default HTTP retry policy).Data: samp_sw_subscription_profile, samp_sw_subscription, samp_saas_feature_usage, samp_sw_unrecognized_subscription_identifier, samp_discovered_user, exclusion rules samp_sw_subscription_id_excl_rule and samp_sw_subscription_user_excl_rule. System properties com.snc.process_flow.reporting.level — set to All for subflow detail; set back afterwards.glide.outbound_http_log.override and glide.outbound_http_log.override.level — temporary detailed outbound logging; turn off afterwards.com.snc.samp.disableeventstorage — when true, usage events are not stored.sn_itam_samp.user_resolution_exclude_table — sys_user extended tables excluded from user matching. Processing rules to remember One connection, one Looker instance; the Connection URL is the Looker base URL.API3 Client ID and secret of a Looker administrator; see_users for download and activity, Admin for reclaim.Roles are read first; each user's license type comes from the roles the user holds.Last activity is the last login, updated only when the daily subscriptions job runs.Reclaim deletes the user and associated records.A default reclamation rule of 60 days is created once. Known limitations The names of the software models and the exact mapping of each Looker license type to a model are not stated in the sources.Whether disabled users are imported is not stated.The login date field, token lifetime, rate limits and the handling of content owned by a deleted user are not documented here.Validation tests only the download calls, not reclaim.Activity inside dashboards and explores is not read. Documentation ServiceNow product documentation for your release: Integrating with Looker and Looker Spoke under Software Asset Management > SaaS License Management.Looker documentation: API3 keys, users, roles, permission sets and model sets.ServiceNow: Configure Now Assist for SAM 10. ServiceNow Otto / Now Assist troubleshooting ServiceNow Otto for Software Asset Management (formerly Now Assist for SAM, application sn_now_assist_sam) adds generative AI help for SaaS integrations. Use it to explain a failed Looker job or a failed connection validation, and to propose user resolution rules when imported subscriptions do not match users. Treat its output as a starting point: confirm every recommendation against the branch in section 5 before changing configuration. How Troubleshoot works 1Failure bannerProfile in Software Asset WorkspaceFailed job or failed Validate Connection 2TroubleshootButton on the error bannerDebug-level validation, ~15–20 s 3Read guidanceError Summary + Suggested ResolutionsMap each item to a section 5 branch 4Fix and validateApply the fix yourselfValidate Connection again; rerun Troubleshoot if needed 5Publish or runPublish new / run existing jobConfirm with section 7 What the AI skills do SkillWhat it doesWhen it runsDefault model providerError log summarizationReads the logs of the failed job or validation and produces an Error SummaryWhen you click TroubleshootAWS Claude (from Australia Patch 4)Error resolution recommendationTurns the summarized errors into Suggested Resolutions, one per errorChained after the summaryAWS Claude (from Australia Patch 4)SaaS user resolutionProposes user resolution rules that map the Looker email to sys_userAutomatically after a subscription download, when prerequisites are metAzure OpenAI The model provider can be changed per skill in the Now Assist Admin console; Now LLM Service can still be selected manually. Before you start Installed and licensed. Otto for SAM (sn_now_assist_sam) is installed and your subscription includes generative AI for SAM. Confirm entitlement with your account team. The capability is not available, or is limited, in in-country, FedRAMP, NSC DOD IL5, IRAP-Protected, self-hosted, regulated-market and other restricted environments.Skills active and displayed. Go to All > Now Assist Admin > Skills, choose the SAM workflow group, open each skill and confirm it is active with Display turned on. To activate: Activate skill > Save and continue > Select display (turn on Display, add roles if needed) > Review and activate > Activate. Skills are active by default from Zurich Patch 4, but a skill you deactivate stays off until reactivated.Roles. sam_integrator to use Troubleshoot and SaaS user resolution; skills are available to sam_user and sam_admin by default. If an administrator changed the skill roles, the custom roles apply instead. Activating or configuring skills needs the Now Assist administrator role.Software Asset Workspace. Troubleshoot appears in the workspace profile form, not in the classic form.Privacy. Inputs and outputs are processed in ServiceNow's generative AI environment and may be processed by the selected third-party model provider. Review your organization's AI data-handling settings and the Now Assist opt-out options before use. Use Troubleshoot on a failed job or validation Go to Workspaces > Software Asset Workspace > License operations > User subscription > Direct integration profiles and open the Looker profile.Existing profile, failed scheduled job: the profile shows an error banner for the failed job. New profile or changed connection: click Validate Connection; a failure shows an error banner.Click Troubleshoot on the banner. Otto runs the validation with debug-level logging, summarizes the errors and proposes resolutions. Expect a response in around 15–20 seconds.Read the Error Summary and Suggested Resolutions on the profile. Map each resolution to the matching branch in section 5 and follow that branch's fix and verify steps.Apply the fix yourself (Troubleshoot never changes connection or integration configuration), then click Validate Connection again. Click Troubleshoot again to regenerate guidance if validation still fails.When validation succeeds, Publish a new profile, or run the job once for an existing profile and confirm the result with section 7. What Troubleshoot writes. The error summary and suggested resolutions are stored on the integration profile, and each run is kept in a troubleshooting log shown as a related tab on the profile. It does not modify subscriptions, credentials or jobs. The AI indicator may not appear on these fields when the system rather than the AI last updated them. What it covers. Runtime failures of the integration's scheduled jobs and connection-validation failures for SaaS and SSO integration profiles. It does not diagnose data-quality questions such as missing users in a product scope, model mapping or reconciliation results; use section 5 for those. AI-generated user resolution rules After each subscription download, SAM checks whether a rule should be generated. The SAM - Generate user resolution rule job calls the SaaS user resolution skill only when at least 10% of subscriptions have no user, and either it is the first run, or the previous run created no rule and the data has changed (a new field or about 10% more user data). Review results: Software Asset Workspace > License operations > SaaS license management > User resolution rules. Rules created by the skill show Source = AI. Steps are listed in the AI activity log in the Activity center on the Software asset overview.Activate deliberately: a generated rule that is inactive shows Review needed. Check it against a few known users, then set it Active and save. Rerun the Looker import to apply it.Each run is logged in samp_user_resolution_rule_log with the outcome. When the assistant does not help What you seeLikely causeWhat to doNo Troubleshoot buttonApplication not installed, skill inactive or Display off, missing role, classic form instead of the workspace, or no current failureCheck the prerequisites above; the button appears only on the error banner of a failed job or validationTroubleshoot runs but returns nothing or an errorSkill call or output formatting failedOpen the generative AI log (sys_generative_ai_log.list) for the skill request: error code, message and whether the response was formatted correctly. Check System Logs > Errors for formatting failuresSummary is short, generic or cut offOlder application version with a smaller output limit, or too little log detailUpdate Otto for SAM to the latest version; rerun Troubleshoot after reproducing the failure so fresh logs existRecommendation contradicts the logsAI output is a suggestion, not a verified diagnosisFollow the outbound HTTP status and the matching section 5 branch; report the mismatch with the generative AI log entryProfile reference fields show invalid field name: troubleshooting_logTroubleshooting component not active on an older SaaS License Management versionUpdate SaaS License ManagementUser resolution job ends with "did not meet the pre-requisites" or "no change in your user data"Expected: fewer than 10% unresolved, or nothing changed since the last runNo action; create a rule manually if needed (branch K)User resolution job ends with "failed due to some error in the Gen AI skill"Skill call or output failedCheck sys_generative_ai_log for the skill runNo rule created: "no user table field could uniquely be identified"the Looker email has no unique exact match in any sys_user fieldCorrect user data or create the rule manually (branch K) Limitations Output is AI-generated and can be inaccurate or incomplete; a person must review it before acting.Only job and validation failures are analyzed; ingestion completeness, mapping, usage and optimization still need section 5.Responses take several seconds because each Troubleshoot click chains more than one model call.Availability depends on your AI entitlement and hosting environment.