Troubleshooting ServiceNow Software Asset Management GitHub Enterprise integration: Complete Troubleshooting Guide; subscriptions, activity 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 GitHub Enterprise integration: subscriptions, activity 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 two GitHub direct integration profiles in SAM: GitHub Cloud Subscription (github_cloud_subscription) for GitHub Enterprise Cloud organizations. It enumerates every organization visible to the authenticated user and reads members, outside collaborators and invitations for each, supports last activity from the organization audit log, and supports reclaim.GitHub Server Subscription (github_server_subscription) for GitHub Enterprise Server. It reads the instance's users with one site-administrator listing, and supports reclaim. It has no activity subflow. Both run on the SaaS License Management subflow framework and call the GitHub Spoke (sn_github_spoke). Each variant has its own alias and credential, so they are configured separately. Sections are marked (Cloud) or (Server) where behavior differs. It does not cover GitHub integrations used for DevOps (Change Velocity, pipelines, source control), GitHub Copilot seat assignment, enterprise-level consumed licenses or the enterprise audit log; the integration does not read them. Applies to: SAM Professional with the Software Asset Management - SaaS License Management (sn_sam_saas_int) Store application and the GitHub Spoke. Behavior can differ between releases: the Cloud last-activity source changed in release 202603. Keep applications current and compare with the release documentation before applying a version-specific conclusion. 2. Implementation checklist CheckWhere and what to inspectReady conditionApplicationsApplication Manager: SaaS License Management with the optional feature GitHub SpokeInstalled and current; update the GitHub Spoke together with SaaS License ManagementRoles (ServiceNow)User creating the profilesam_integrator or sam_adminGitHub plan (Cloud)GitHub organizationGitHub Enterprise plan; free or non-enterprise organizations fail (the audit log returns 404 on free plans)GitHub role (Cloud)GitHubOrganization owner of every organization to track, for all three processesGitHub role (Server)GitHub Enterprise ServerSite administrator for download and reclaimToken typeGitHub > Settings > Developer settings > Personal access tokensTokens (classic), not fine-grainedCloud scopesSameread:org (download), read:org and read:audit_log (activity), write:org (reclaim); the setup guide enables repo, read:org, write:org and read:audit_log on one token, and validation also reads repositoriesServer scopeServer token pagesite_adminSAML single sign-onGitHub token page > Configure SSOThe token is authorized for each organization that enforces SAMLToken expiryToken ExpirationA date you track; an expired token fails every callProfileSoftware Asset Workspace > License operations > User subscriptions > Direct integration profiles > New > GitHub Cloud (or GitHub Server)Download subscriptions (locked on); Download activity (Cloud, default on); Reclaim subscriptions (default on)AliasProfile Connection & CredentialSet on Save: sn_github_spoke.GitHub (Cloud) or sn_github_spoke.GitHub_Server (Server)Connection (Cloud)Alias > Create New Connection & CredentialConnection URL host api.github.com; API Key = the tokenConnection (Server)SameYour GitHub Enterprise Server API host reachable from the instance, or Use MID Server set to true when the host is internalAPI key formatConnection recordGitHub Spoke 2.2.5 or later: the raw token. Earlier spokes: Bearer <token>Activity windowProfile Analyze user activity fromDefault 60 days; set it no more than about 7 days back to avoid slow activity runs (GitHub keeps audit log events for 7 days)Pending collaboratorsSystem property sn_sam_saas_int.pull_pending_collaborator_githubfalse (default) unless pending outside collaborators must be countedValidation and publishProfile > Validate Connection, then PublishValidation succeeds; jobs created only after validationJobsProfile > Scheduled JobsSAM - Refresh <name> Subscriptions and, for Cloud with activity, SAM - Refresh <name> Activity; active, no duplicates What happens when a setting is missing or wrong Setting, field or propertyIf it is missing or wrongTypical symptomGitHub Spoke not selected as an optional featureProfile types and aliases missingGitHub Cloud or GitHub Server missing from New on Direct integration profilesFine-grained token usedRequired scopes are not availableAuthorization or scope failuresToken not authorized for SAML SSOGitHub refuses the organizationMethod failed: (/orgs/<org>) with code: 403 - Forbidden username/password combo with Resource protected by organization SAML enforcement. You must grant your Personal Access token access to this organization.Token from someone who is not an organization ownerOrganization data or removal refusedYou must be an owner of this organization to remove outside collaboratorsToken without repo or repository read accessCloud validation reads repositoriesValidation fails although members can be readToken without read:audit_logAudit log refusedHTTP 403 on activity; last activity blankToken without write:orgRemoval refusedReclaim fails after a successful validationOrganization on a free planAudit log not availableHTTP 404; that organization is skipped for activityCloud connection host not api.github.comThe profile cannot be savedThe Connection URL is incorrect. Delete the connection and recreate it to proceed further.API key entered as Bearer <token> on spoke 2.2.5 or later (or the raw token on an older spoke)Authentication failsInvalid Credentials. Check with your System Administrator.Server host unreachable from the instanceCalls cannot be madeTimeout or connection errors; use a MID Server for internal hostsToken expiredEvery call is refusedHTTP 401 on the first requestAfter an upgrade to 202603 or later, token lacks read:audit_logActivity fails silentlyThe profile warning about the audit log scope; last activity stops updatingpull_pending_collaborator_github set to true on a large organizationOne request per repositoryRate limiting and long runsDownload activity clearedActivity job not created or deletedNo activity job; last activity blankReclaim 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 againSpoke older than 2.2.7Pagination or failure handling incompleteMissing members on large organizations; job shows success while an organization call failedDebug properties left onExtra loggingSlow instance after troubleshooting 3. Symptoms and expected behavior SymptomFirst branchHealthy evidence to seekGitHub option, spoke or jobs missingAProfile types available, jobs listedCannot publish, URL rejected, back in DraftBStatus Published with its jobsValidate Connection failsCValidation successful401, 403, SAML, token errorsDRequests return 200Owner or role errorsEOrganization requests succeed for every organizationServer connection problemsFUsers listing returns usersRefresh job failed, or succeeded with nothingGCompleted job with subscriptionsFewer or more subscriptions than GitHub showsHCounts match organization seat usageSeveral organizations, same user in severalIOne subscription, one license per organizationModel, identifier or entitlement problemsJGitHub model on every subscriptionUser empty or wrongKIntended sys_user linkedLast activity blank or staleLRecent audit-log activityActivity job errorsMActivity job completesNo or false reclamation candidatesNCandidates only for truly inactive usersReclaim failsOUser removed from the organizationRate limits and long runsPNormal run durationWarning about the audit log scope after an upgradeQWarning cleared after saving the new tokenProblems after clone or repairRValidated profile, valid tokens A healthy Cloud download creates one subscription per user across all organizations visible to the token: members, outside collaborators and pending invitations. A user who appears in several roles is pulled once, with priority member, outside collaborator, pending invitation, pending outside collaborator. 4. Execution path and evidence correlation Hover or tap a step to see what breaks there; click it to open the matching branch.SetupConnectionCollectionMatchingWriteDownstream Cloud: subscription downloaddaily 1Published profileGitHub Spoke selected, alias sn_github_spoke.GitHub, validatedBreaks here: Spoke missing, URL rejected, DraftOpen branch B →2Refresh jobSAM - Refresh <name> SubscriptionsBreaks here: Success with nothing; Failed to downloadOpen branch G →3Classic tokenOrg owner; read:org; SAML SSO authorizedBreaks here: 403 SAML; Invalid CredentialsOpen branch D →4Owner and scopesrepo, read:org, read:audit_log, write:orgBreaks here: Must be an owner; 403Open branch E →5OrganizationsEvery organization visible to the token userBreaks here: Organization missingOpen branch H →6PeopleMembers, outside collaborators, invitations (pending outside collaborators if the property is true)Breaks here: Pending users missing; suspended accounts countedOpen branch H →7One record per userRole priority; one license per organizationBreaks here: Same user in several organizationsOpen branch I →8Model and userGitHub model; login or email to sys_userBreaks here: Empty user; unrecognized identifierOpen branch K →9Upsert and cleanupDeactivate, upsert, delete users not returnedBreaks here: Disappearing subscriptionsOpen branch H → Cloud: activity and reclaimdaily 1Activity jobSAM - Refresh <name> Activity after a good downloadBreaks here: Job missing; scope warning after upgradeOpen branch Q →2Audit log/orgs/<org>/audit-log, cursor paging, 7-day retentionBreaks here: 404 free plan; 403 scope; 429Open branch M →3Last activityActor and time, moves forward onlyBreaks here: Blank or stale activityOpen branch L →4CandidatesRule per product; best-effort activityBreaks here: False or missing candidatesOpen branch N →5ReclaimRemove member or outside collaborator from the organizationBreaks here: Must be an owner; 422; 404Open branch O →6After clone or repairTokens re-entered, spoke updatedBreaks here: Missing buttons, stale tokensOpen branch R → Serverdaily 1Published profilealias sn_github_spoke.GitHub_ServerBreaks here: URL rejected on older versionsOpen branch B →2ReachabilityServer API host; Use MID Server when internalBreaks here: Timeouts; HTTP 202 on older spokesOpen branch F →3Site admin tokensite_admin scopeBreaks here: Authorization errorsOpen branch D →4Users listingOne instance-wide site-administrator listingBreaks here: Missing usersOpen branch H →5ReclaimRemove the user (site admin)Breaks here: Not covered by validationOpen branch O →6No activityNo Server activity subflowBreaks here: Expected: blank activityOpen branch L → Cloud subscription download path Subscriptions job → profile and classic token → organizations visible to the authenticated user → for each organization: plan, members, outside collaborators, invitations (and pending outside collaborators if the property is true) → one subscription per user (role priority) → delete users not returned → reclamation rules → user resolution Cloud activity and reclaim path Activity job (only after a good download) → for each organization: plan and audit log (per page, cursor-based) → actor and time → last activity moved forward and events recorded → candidates → reclaim: remove the member or outside collaborator from the organization Server path Subscriptions job → site-administrator users listing → upsert → delete users not returned → reclaim: remove the user. There is no activity step for Server. StageRecord or source to inspectBehaviorJobsProfile > Scheduled JobsCreated on publish: a subscriptions job and, for Cloud with activity, an activity job. They run immediately and then dailyJob resultProfile > Scheduled Job Results (sam_saas_job_log) and the red banner on the profileStatus and message of each runOrganizationsList organizations for the authenticated userAn organization the token's user does not belong to or own is not seenPlanOrganization plan lookupThe plan decides whether the audit log is availableMembers and collaboratorsOrganization members, outside collaborators, invitationsRole priority applies; one license is counted per organizationActivityGET /orgs/{org}/audit-log (page size, after cursor)Actor becomes the user principal name, actor ID the external user ID, event time the last activity; events without an actor are skippedReclaimRemove organization member or outside collaboratorRemoves the user from the organization; GitHub account stays Correlate one execution before deciding a cause Record the job, profile, variant, start and end in UTC, and the versions of SaaS License Management and the GitHub Spoke.Open the profile's Scheduled Job Results (sam_saas_job_log) and read the message.Open Flow Designer > Executions for GitHub Cloud Download Subscriptions (or GitHub Server Download Subscriptions) and for GitHub Cloud Update User Activity; find the failing step. A job can show success while an organization call failed, so always read the flow execution.Open System Logs > Outbound HTTP Requests filtered on URL contains github; read status and response body.For deeper tracing, temporarily set com.snc.process_flow.reporting.level to All, glide.outbound_http_log.override to true and glide.outbound_http_log.override.level to all, rerun once, then set them back. 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 <org>, <name> or <token> are placeholders; keep the real values private. Start every investigation here 1Job resultProfile > Scheduled Job Results (sam_saas_job_log)Status and message; Completed can hide a failed organization call 2Flow executionFlow Designer > GitHub subflowThe failing organization step and error 3Outbound HTTPURL contains githubStatus and GitHub error body 4Pick a branchMatch the message belowSAML 403 → D, must be an owner → E, URL rejected → B, 404 audit log → M Start every investigation the same way. (1) The profile's Scheduled Job Results (sam_saas_job_log) or the red banner on the profile. (2) Flow Designer > Executions for the GitHub subflow at the same time. (3) System Logs > Outbound HTTP Requests with URL containing github. Read the response body, not only the status code. Confirm first whether the profile is Cloud or Server. A. GitHub option, spoke, subflows or jobs are missingB. The profile cannot be saved or published, or returns to DraftC. Validate Connection failsD. Token, SAML and authentication errorsE. Organization owner and scope errorsF. GitHub Enterprise Server connection problemsG. The refresh job fails, or succeeds with nothingH. Fewer or more subscriptions than GitHub showsI. Several organizations, and the same user in severalJ. Identifier, software model or entitlement problemsK. Subscription user is empty or wrongL. Last activity is blank or staleM. Activity job errorsN. No reclamation candidates, or false candidatesO. Reclaim failsP. Rate limits and long runsQ. Warning about the audit log scope after an upgradeR. Problems after a clone or repair A. GitHub option, spoke, subflows or jobs are missing Symptoms. GitHub Cloud or GitHub Server is not offered when creating a direct integration profile.Installing SaaS License Management fails with a dependency error on a GitHub Spoke version that is no longer available.No SAM - Refresh <name> Subscriptions job after publishing. Where to check. Application Manager > SaaS License Management > optional features; installed applications for the GitHub Spoke; the profile's Scheduled Jobs list. Causes and fixes. Spoke not selected. In Application Manager open SaaS License Management, choose Install optional features and select GitHub Spoke. Without it the profile types and aliases do not exist.Dependency error on install. Install or update the GitHub Spoke to the current Store version first, then SaaS License Management; if the Store offers only a withdrawn version, open a support case.Core UI create option inactive. With Software Asset Workspace installed, create the profile from License operations > User subscriptions > Direct integration profiles > New.Upgraded from Yokohama or Zurich (Cloud). Reconfigure the Cloud profile and re-enter the connection.Jobs not created. Jobs are created only after validation and publish (B). Verify. The profile shows Published with its Scheduled Jobs. B. The profile cannot be saved or published, or returns to DraftThe Connection URL is incorrect. Delete the connection and recreate it to proceed further.The connection record is not associated with the Connection and credential field. Create the connection to proceed further.Application is set to <scope> scope. Switch to 'Global' application scope to publish this integration profile. Symptoms. The Connection URL is incorrect. Delete the connection and recreate it to proceed further.The connection record is not associated with the Connection and credential field. Create the connection to proceed further.Application is set to <scope> scope. Switch to 'Global' application scope to publish this integration profile.No Publish button, or a published profile is back in Draft. Where to check. Profile form (Status, Connection & Credential); the connection record; the application scope picker. Causes and fixes. Cloud host. The Cloud connection URL host must be api.github.com. Delete the connection and recreate it with that host.Server host (older versions). Older versions also compared the Server URL to api.github.com and rejected every self-hosted host; update SaaS License Management. Recreating the connection does not help.No connection. Open the alias from the profile and use Create New Connection & Credential (Connection Name, Connection URL, Use MID Server, API Key).Wrong scope. Switch to Global and publish.Not validated. Publish appears only after Validate Connection succeeds (C).Edited after publish. Clearing Download activity returns the profile to Draft, shows Validate again and deletes the activity job; validate and publish again. Verify. Status Published; the subscriptions job and, for Cloud with activity, the activity job listed. C. Validate Connection failsConnection validation is not successful. Please check connections and credentials and try again.Connection validation failed. Verify the configurations you have provided and then retry.Connection validation is not successful. Invalid inputs passed to action. Please check the action. Symptoms. Connection validation is not successful. Please check connections and credentials and try again.Connection validation failed. Verify the configurations you have provided and then retry.Validation fails for a token that can read members but not repositories.Connection validation is not successful. Invalid inputs passed to action. Please check the action. Where to check. Flow Designer execution of the validation; the outbound log; the token's scopes and the organizations it can see. Causes and fixes. What Cloud validation reads. In order: the organizations of the authenticated user, each organization's plan, its repositories, invitations, members and outside collaborators. With Download activity selected it also reads the plan, the authenticated user and the organization audit log. A token that cannot read repositories or invitations fails validation even if members are readable, and a token without read:audit_log passes subscription validation but fails activity validation.What Server validation reads. The site-administrator users listing only.Reclaim is not validated. A token without write:org passes validation and fails later at reclaim.Token problems. See D and E.Date format. A date-format parsing error can occur during validation. If validation fails with a date or query parsing error, set glide.sys.date_format to yyyy-MM-dd and validate again.Where Now Assist for SAM is available, use Troubleshoot on the validation error banner (section 10). Verify. Validation successful and the Publish button appears. D. Token, SAML and authentication errorsMethod failed: (/orgs/<org>) with code: 403 - Forbidden username/password comboResource protected by organization SAML enforcement. You must grant your Personal Access token access to this organization.Invalid Credentials. Check with your System Administrator.Bad credentials Symptoms. Method failed: (/orgs/<org>) with code: 403 - Forbidden username/password comboResource protected by organization SAML enforcement. You must grant your Personal Access token access to this organization.Invalid Credentials. Check with your System Administrator.HTTP 401 Bad credentials on the first request. Where to check. The token page in GitHub (type, scopes, expiration, SSO); the API Key on the connection; the spoke version. Causes and fixes. SAML enforcement. In GitHub open Settings > Developer settings > Personal access tokens > Tokens (classic), choose Configure SSO next to the token and Authorize each required organization. Confirm the token owner is an organization owner, then validate again.Fine-grained token. Use a classic token; the integration needs classic scopes.Wrong key format. On GitHub Spoke 2.2.5 or later enter the raw token; on earlier spokes enter Bearer <token>. A wrong form gives Invalid Credentials.Expired or revoked token. Generate a new classic token with the scopes in section 2 and update the connection credential.Server token. Create it on the Server host's own token page with the site_admin scope.Scopes. Missing scopes produce 403; see E. Verify. The first organization request returns 200 and validation succeeds. E. Organization owner and scope errorsYou must be an owner of this organization to remove outside collaborators Symptoms. You must be an owner of this organization to remove outside collaboratorsHTTP 403 on the audit log, on members or on removal.Some organizations are missing from the results. Where to check. The token owner's role in each organization; the token's scopes; the organization list the token can see. Causes and fixes. Not an organization owner. All three processes need an organization owner. Regenerate the token from an owner account and update the connection.Organization not visible. The integration enumerates the organizations the authenticated user belongs to; an organization the token's user is not a member or owner of is not tracked. Add the user as an owner of every organization.Scope missing. read:org (download), read:audit_log (activity) and write:org (reclaim); add the missing scope and update the token.SSO not authorized. See D1.Server. The account must be a site administrator with the site_admin scope for all processes. Verify. Requests for every organization return 200, and the organization list matches what you expect. F. GitHub Enterprise Server connection problems Symptoms. Timeouts or connection errors from the instance to the Server host.The Connection URL is rejected on publish (older versions).Only members of the Server instance appear; no activity. Where to check. The connection record (URL, Use MID Server); the outbound log; MID Server status. Causes and fixes. Host reachability. The instance must reach your Server's API host. If the host is internal, set Use MID Server to true on the connection and make sure a MID Server is installed and can reach the host.Connection URL. The setup documentation shows https://api.github.com in its Server example, which applies to Cloud; for Server use the API address of your own GitHub Enterprise Server instance.Older versions. Publishing failed with The Connection URL is incorrect. Delete the connection and recreate it to proceed further. for self-hosted hosts; update SaaS License Management.HTTP 202 (older spokes). Server can answer 202 while preparing a response, and older spokes treated it as a failure; update the GitHub Spoke and rerun after a short wait.Token and role. Site administrator and site_admin (D, E).No activity for Server. The Server profile has no activity subflow, so last activity is not populated; this is not a failure. Verify. The Server users listing returns users and the job completes. G. The refresh job fails, or succeeds with nothingFailed to download subscriptions.The subflow couldn't find an action it is trying to use. Make sure you are on the latest version of the store app the subflow depends on.Cannot find function <name> in object [object Object]Unable to match value 'undefined' with field 'profile_type' in table 'samp_sw_subscription_integration'. Expecting type 'string' Symptoms. Scheduled Job Results shows Failed with: Failed to download subscriptions.The subflow couldn't find an action it is trying to use. Make sure you are on the latest version of the store app the subflow depends on.Cannot find function <name> in object [object Object]Unable to match value 'undefined' with field 'profile_type' in table 'samp_sw_subscription_integration'. Expecting type 'string'Or the job shows Completed with zero subscriptions and no error. Where to check. The job result; the failing step in the Flow Designer execution; the outbound log. Causes and fixes. Success with nothing. In spokes older than 2.2.6 the job reported success even when the organization call failed. Read the flow execution and the outbound log rather than the job status, and update the GitHub Spoke.Underlying GitHub error. Fix the step error (D, E, F, P).Outdated application or spoke. Update SaaS License Management and the GitHub Spoke together, then run each job once.Retired action in a subflow. Update the subflow to the current action, or create a new profile from the updated application, republish and rerun.Customized subflow. Revert to the out-of-box subflow.Overlapping runs. Do not run the subscriptions and activity jobs at the same time. Verify. The next run shows Completed and updated subscriptions. H. Fewer or more subscriptions than GitHub shows Symptoms. Members missing on large organizations; pending invitees or outside collaborators missing; suspended or inactive accounts counted as users; counts differ from the organization's seat usage. Where to check. The organization's People page and seat usage; the organization list for the token; the system property; exclusion rules. Causes and fixes. Organization not visible. See E2.Pending outside collaborators. They are pulled only when sn_sam_saas_int.pull_pending_collaborator_github is true (default false). Set it to true and rerun if they must be counted. Invitations and outside collaborators are always read.Role priority. A user in several roles in one organization is pulled once and one license is counted: member first, then outside collaborator, pending invitation, pending outside collaborator.Inactive or suspended accounts. GitHub replaces the login of inactive or suspended accounts with a generated identifier, and the Cloud integration can import them as active subscriptions; a fix is planned but not shipped. Exclude or delete those subscriptions (for example with a user exclusion rule matching the generated identifier pattern) and review them before reclaiming.Pagination (older spokes). Update the GitHub Spoke to 2.2.7 or later if large organizations are missing members, then compare counts with the organization's seat count.Exclusion rules. Subscription Identifier Exclusion Rule and Subscription User Exclusion Rule silently drop matching rows.Failed run. A failed run restores active flags but does not undo deletions already made; fix the cause and rerun. Verify. Counts per organization match GitHub's seat usage, and a missing user appears after the next run. I. Several organizations, and the same user in several Symptoms. A user is a member of several organizations but has one subscription record; license counts are higher than the number of records; reclaim removes the user from one organization and fails for the others. Where to check. The user's memberships in each organization; the subscription's licensing results. Causes and fixes. One record, several licenses. When the same user is a member of several organizations on the same plan type, only one subscription record is created but one license is consumed per organization. This is how GitHub licenses and how SAM currently counts it.Reclaim in several organizations. Reclaim removes the user from the intended organization; the step for the other organizations can fail. There is no workaround in the sources; remove the user from the remaining organizations in GitHub and close the candidate.Organizations tracked. Only organizations the token's user owns or belongs to are counted (E2). Verify. License counts per organization match GitHub; reclaim candidates are reviewed by organization. J. Identifier, software model or entitlement problems Symptoms. A raw identifier and no software model; entries under Unrecognized Subscription Identifiers; compliance shows nothing. Where to check. Profile > Software Models and Unrecognized Subscription Identifiers; entitlements. Causes and fixes. Content out of date. Download current subscription-identifier content.Unknown identifier. Open it under Unrecognized Subscription Identifiers, set the correct software model and save.Entitlements missing. Software models and reclamation rules are created automatically; entitlements are not. Create them and run reconciliation.Not covered. Copilot seats and enterprise consumed licenses are not read by this integration. Verify. Subscriptions show the GitHub model and reconciliation produces results. K. Subscription user is empty or wrong Symptoms. Subscriptions with a login but no User; rules on email or username do not apply; records on the Subscriptions without user page. Where to check. sys_user fields versus the GitHub login or email; User resolution rules; sn_itam_samp.user_resolution_exclude_table. Causes and fixes. No match. GitHub often provides no real email or principal name. Create a user resolution rule (Software Asset Workspace > License operations > User subscription > User resolution rules) that targets a field the GitHub profile actually fills, such as the login, then rerun the refresh job.Rules ignored when the principal name is empty (older versions). Update SaaS License Management.Generated identifiers. Suspended accounts carry a generated identifier as their name (H4); they will not resolve.Activity events. Events without an actor or actor ID are skipped and cannot update last activity.Same value in several user tables. List the extra tables in sn_itam_samp.user_resolution_exclude_table. Verify. The subscription shows the intended user. L. Last activity is blank or stale Symptoms. Cloud subscriptions have no last activity or it does not move; users who work daily are flagged for reclaim; the Server profile never shows activity. Where to check. The activity job result; the organization's plan; the token's read:audit_log scope; the release version. Causes and fixes. Server has no activity. Expected (F6).Audit log source (release 202603 and later). Activity comes from the organization audit log and needs a classic token with read:audit_log and an Enterprise plan. Older releases used the organization events API, which returned only the latest 45 events with no incremental pull and produced stale activity and false reclamation candidates; update to 202603 or later.Free-plan organizations. The audit log returns 404, and that organization is skipped.Scope missing after an upgrade. See Q.Seven-day retention. GitHub keeps audit log events for seven days. If the activity job fails for seven or eight days in a row, older events cannot be recovered and last activity can be wrong.Look-back. The profile's Analyze user activity from default is 60 days; set it no more than about seven days back.Never cleared. Last activity only moves forward. Verify. A user who was active yesterday shows a recent last activity after the next activity run. M. Activity job errors Symptoms. HTTP 404 on /orgs/<org>/audit-log.HTTP 403 on the audit log.HTTP 429 while paging the audit log.The activity job fails while the subscription job succeeds. Where to check. The activity flow execution (Update User Access, Look up Organization Audit Log Stream); the outbound response body. Causes and fixes. 404. The organization is on a free plan; the audit log needs Enterprise. The integration logs the error and skips that organization.403. The token lacks read:audit_log; regenerate the token with the scope and update the connection and credential.429. GitHub allows about 1,750 requests per hour for a user and IP address. The subflow pauses and retries after the reset, and remaining pages are deferred to the next scheduled run.Expired cursor. The subflow falls back to a full pull from the start of GitHub's retention window, which uses more requests.Events without an actor. They are skipped.Older spokes. Update the GitHub Spoke. Verify. The activity job completes and last activity updates. N. No reclamation candidates, or false candidates Symptoms. An inactive user gets no candidate; active users are proposed for removal. Where to check. The GitHub reclamation rule; subscriptions' user and last activity; the activity source (L). Causes and fixes. Last activity unreliable. Fix L first. Best-effort activity can drop events, so review GitHub candidates before acting. A user with no stamped activity is not proof of inactivity.Rule configuration. Confirm Create reclamation candidate is checked, the threshold is what you want (for example 30 days when a user inactive for 31 days has no candidate) and the subscription condition matches.User empty. With Notify user on, a candidate without a user goes to Attention Required; fix K.Group-derived subscriptions. Subscriptions added through groups are not generated as reclamation candidates.Do not enable automatic reclaim blindly. False candidates have removed active users on older releases. Verify. A user inactive beyond the threshold receives one candidate; active users do not. O. Reclaim failsYou must be an owner of this organization to remove outside collaboratorsResource not foundThe reclamation of user subscriptions will not be successful because the Reclaim subscription checkbox isn't selected on the integration profile. Symptoms. You must be an owner of this organization to remove outside collaboratorsHTTP 422: the user is a member but was reclaimed as an outside collaborator.HTTP 404 Resource not found.The reclamation of user subscriptions will not be successful because the Reclaim subscription checkbox isn't selected on the integration profile. Where to check. The red banner on the candidate; the Reclaim Subscription flow execution; the outbound response; the user's role in GitHub. Causes and fixes. What reclaim does. It removes the member or outside collaborator from the organization; the GitHub account stays. Cloud needs an organization owner token with write:org; Server needs a site administrator with site_admin.Reclaim not configured. Select Reclaim subscriptions, validate and publish.Not covered by validation. Test with one candidate.403 owner error. The token owner is not an organization owner of that organization; regenerate the token as an owner.422. The user is a member, not an outside collaborator. Mark the candidate Closed Complete and run the profile's scheduled jobs so roles refresh.404. The user is not in the organization, or their role changed from member to outside collaborator. Run the scheduled jobs to refresh roles and retry.User outside your organizations. If the user belongs to an organization the connecting account cannot reach, remove the user manually in GitHub and close the candidate.Several organizations. See I2. Verify. The user is removed from the organization in GitHub, the candidate closes and the subscription updates on the next run. P. Rate limits and long runs Symptoms. HTTP 429 or 403 rate-limit responses; very long runs; failures near the end of large downloads. Where to check. The outbound log statuses and timing; the repository count; the property value. Causes and fixes. Pending collaborators. With sn_sam_saas_int.pull_pending_collaborator_github set to true, the integration makes one request per repository; on organizations with many repositories this causes rate limiting. Set it to false if users are missing or throttling appears and you do not need pending outside collaborators.Audit log limit. About 1,750 requests per hour per user and IP address; see M3.Several profiles on one account. Do not run several profiles against the same GitHub account at the same time; stagger them and run off-peak.Pagination fixes. Update the GitHub Spoke (2.2.7 or later).Flow reporting overhead. Keep com.snc.process_flow.reporting.level at OFF in production. Verify. A complete run without unhandled 429 and a normal duration. Q. Warning about the audit log scope after an upgradeThis integration has been upgraded to use the GitHub Audit Log API, which requires an updated permission scope (read:audit_log). Please update your Personal Access Token and connection credentials to continue receiving accurate user activity data. Symptoms. Profile warning: This integration has been upgraded to use the GitHub Audit Log API, which requires an updated permission scope (read:audit_log). Please update your Personal Access Token and connection credentials to continue receiving accurate user activity data.Last activity stops updating after an upgrade and false candidates return. Where to check. The profile form for the warning; the token's scopes; the upgrade fix script's result. Causes and fixes. Why it appears. After the upgrade to 202603 or later a fix script flags Published and Draft Cloud profiles as needing a scope update.Fix. Generate a new classic token with read:audit_log (and the other scopes in section 2), update the connection and credential, then save or validate; the flag clears.Warning dismissed or script not run. The activity subflow then fails silently and last activity stops; the warning reappears on the next profile interaction. Check the scope even when no warning is shown.Profiles in other states. They are not flagged; add the scope before publishing. Verify. The warning is gone and last activity updates after the next activity run. R. Problems after a clone or repair Symptoms. Tokens fail after a clone; the profile form is missing fields; Validate or Publish is missing after an upgrade. Where to check. Installed versions; customizations of SaaS License Management; token records; 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.Credentials after a clone. Tokens are instance-specific; enter the token again on the target instance or disable the jobs there.Upgrade fix jobs. They run as scheduled jobs; let them finish.Versions out of step. Update SaaS License Management and the GitHub Spoke together.Alias or connection broken. Recreate the connection on the shipped alias and validate again. Verify. Validation succeeds and the jobs complete in the target instance. 6. Cause-specific correction and controlled recovery Validation, publish, downloads, activity runs and reclaim are write operations; obtain approval before running them in production. Established causeCorrection ownerControlled recovery and stop conditionApplications or spokeServiceNow platform administratorInstall or update together, validate, publishToken type, scopes, SSO or expiryGitHub organization owner and integration ownerCreate a classic token with the scopes, authorize SSO, update the connectionOrganization visibilityGitHub organization ownerMake the token's user an owner of every organizationServer connectionPlatform and network teamReachable host or MID Server, correct URL, validateCoverage (pending collaborators, suspended accounts, pagination)Integration ownerAdjust the property, update the spoke, run once, compare countsMapping and user resolutionSAM administratorMap identifiers or add rules, rerunActivitySAM integration ownerNew token with read:audit_log, run after a good downloadReclaimSAM process owner and GitHub organization ownerReclaim one candidate first; handle several organizations manuallyClone, upgrade, repairPlatform ownerRestore out-of-box components, re-enter tokens, validate, run once 7. Verification criteria and recovery evidence Verification layerEvidence requiredWhat does not satisfy itConfigurationPublished profile, classic token authorized for SSO, every organization visibleA Published status after an unvalidated connection changeExecutionCompleted sam_saas_job_log row and a successful flow execution for each organizationA job status of Completed aloneCoverageSubscriptions per organization match GitHub's seat usageTotals that include suspended accounts or ignore pending collaboratorsMatchingModel and user on every subscriptionRaw identifiers as display namesActivityRecent audit-log activity for an active userBlank activity read as inactivityReclaimOne reclaimed user removed from the organization in GitHubCandidate closed without the GitHub change 8. Escalation evidence to collect Versions of SaaS License Management, the GitHub Spoke and the platform; recent upgrades, repairs or clones.Variant (Cloud or Server), number of organizations, the GitHub plan, token type, scopes and the token owner's role (no token values).Profile status, selected options, the property value for pending collaborators.Job name, run time in UTC, sam_saas_job_log status and message.The failing Flow Designer step and error.Outbound log entries: URL path with the organization replaced by a placeholder, status and the GitHub error body (no tokens).Counts per organization in GitHub and in ServiceNow; one affected user's role (no names).Steps already taken and results. Never include tokens, organization names or user names in shared evidence. 9. References, processing rules and known limitations Key records Jobs: SAM - Refresh <name> Subscriptions, SAM - Refresh <name> Activity (Cloud).Subflows: GitHub Cloud Download Subscriptions, GitHub Server Download Subscriptions, GitHub Cloud Update User Activity (with GitHub Update User Access), GitHub Cloud Reclaim Subscription, GitHub Server Reclaim Subscription.Spoke: aliases sn_github_spoke.GitHub and sn_github_spoke.GitHub_Server.Data: samp_sw_subscription_profile, samp_sw_subscription, sam_saas_job_log, 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 sn_sam_saas_int.pull_pending_collaborator_github — set to true to pull pending outside collaborators (default false).com.snc.process_flow.reporting.level — All while tracing, OFF otherwise.glide.outbound_http_log.override and glide.outbound_http_log.override.level — temporary detailed outbound logging; turn off afterwards.sn_itam_samp.user_resolution_exclude_table — sys_user extended tables excluded from user matching. Processing rules to remember Cloud: every organization visible to the token is processed; Server: one instance-wide users listing.A user in several roles in one organization is pulled once (member, outside collaborator, pending invitation, pending outside collaborator).A user in several organizations has one subscription record and one license per organization.Activity (Cloud only) comes from the organization audit log from release 202603; GitHub keeps events for seven days.Reclaim removes the user from the organization; the GitHub account stays.Validation does not test reclaim. Known limitations Inactive or suspended GitHub accounts can import as active subscriptions; a fix is planned.Multi-organization reclaim can fail for the other organizations; no workaround is documented.Last activity is best-effort and can drop events; review candidates before acting.Copilot seats and enterprise-level licenses are not read. Documentation ServiceNow product documentation for your release: Integrate with GitHub Cloud and Integrate with GitHub Server under Software Asset Management > SaaS License Management.GitHub documentation: personal access tokens (classic), SAML single sign-on authorization, the organization audit log and API rate limits.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 GitHub Enterprise 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 GitHub login 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 GitHub Enterprise 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 GitHub Enterprise 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 GitHub login 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.