Troubleshooting ServiceNow Software Asset Management: Jira Software Cloud integration: Complete troubleshooting GUIDE; subscriptions or activity missingSummary :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 Jira Software Cloud integration: subscriptions or activity missing 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 Jira direct integration profile (profile type jira_subscription, label Jira Subscription) for Jira Cloud. It runs on the SaaS License Management subflow framework: the profile's subflows call the Jira Spoke (sn_jira_spoke) and read Jira through the Atlassian API. The profile has three capabilities: download subscriptions (mandatory), download activity and reclaim subscriptions. How subscriptions are built. The integration is group-based. Only users who belong to the Jira groups you select on the connection are imported, and every selected group maps to the same product, Atlassian Jira Cloud (identifier JIRA_SOFTWARE). Jira Service Management and Work Management seats are not distinguished. The profile does not use the Atlassian organization admin API or an organization API key. The same profile type also supports Jira Server and Data Center through a server_type connection attribute (cloud or server); those differences are not covered here. It does not cover Confluence Cloud (a separate article), Jira used for ITSM integration, or Atlassian single sign-on. Applies to: SAM Professional with the Software Asset Management - SaaS License Management (sn_sam_saas_int) Store application and the Jira Spoke. Setup and scopes differ between SaaS License Management 17.4.0 and earlier and 17.4.1 and later; both are described. 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 Jira SpokeInstalled and currentIntegration HubSubscription and pluginsActive; the spoke needs an Integration Hub subscriptionRoles (ServiceNow)User creating the profilesam_integrator or sam_admin; editing aliases needs admin. The group picker needs sn_jira_spoke.jira_adminJira permissions: downloadJira administrationPermission to access Jira and the Browse users and groups global permissionJira permissions: activitySameAdminister Jira global permission, Browse Projects for the project containing the issue, and issue-level security permission if issue security is configuredJira permissions: reclaimSameSite administration (member of the site-admin group)AuthenticationAtlassian accountEither an API token for an account with the permissions above (Basic), or an OAuth 2.0 (3LO) appCloud IDAtlassian Administration > select the organization > Apps > Atlassian apps > Manage app on the Jira rowThe Cloud ID is the last part of that page's address; one Cloud ID is one siteRequired propertySystem Propertiescom.glide.transform.json.max-partial-length set to 32768 (needed for the activity subflow)ProfileSoftware Asset Workspace > License operations > User subscriptions > Direct integration profiles > New > JiraDownload subscriptions (mandatory), Download activity (default on), Reclaim subscriptions (default on)AliasProfile Connection & CredentialSelected automatically on Save by the checkboxes: sn_jira_spoke.jira_subscription_activity_reclaim (both), ...jira_subscription_activity, ...jira_subscription_reclaim, or ...jira_subscriptionConnectionAlias > Create New Connection & CredentialBasic: Connection URL https://api.atlassian.com/ex/jira/<Cloud-ID>, User Name = the account email, API Key = the API token. OAuth: see branch E. API Version attribute presentJira groupsJira > Jira Groups > Add GroupsThe groups that grant Jira product access moved to Selected, using the same Connection & Credential as the profileValidation and publishProfile > Validate Connection, then PublishValidation succeeds; Publish appears only after a successful validationJobsProfile > Scheduled JobsSAM - Refresh <name> Subscriptions and, with activity, SAM - Refresh <name> Activity; active, no duplicates, Run as emptyMultiple sitesParent alias sn_jira_spoke.Jira > Child AliasesOne child alias, connection and profile per Jira site What happens when a setting is missing or wrong Setting, field or propertyIf it is missing or wrongTypical symptomJira Spoke not selected as an optional featureProfile type and subflows missingJira is missing from New on Direct integration profilesNo groups selected under Jira GroupsDownload iterates over nothingJob completes with zero users and no errorUser without sn_jira_spoke.jira_admin opens the group pickerPicker shows nothingCannot select groupsAPI token revoked, or wrong email or Cloud IDJira rejects the callUnauthorized - Incorrect username and / or password. or Could not authenticate the request.Connection URL without the Cloud IDRequest goes to the wrong siteHTTP 404 or an HTML page instead of JSONAPI Version attribute missing from the connection (often on an imported or cloned child alias)Request path has no versionHTTP 404 on /rest/api//group/member and JSON must be an object or an array: '<'Activity permissions missing (Administer Jira, Browse Projects)Audit log and issue search refusedLast activity blank; 403 on the audit logcom.glide.transform.json.max-partial-length missing or too lowLarge JSON responses are truncatedActivity subflow fails to parse and updateReclaim permissions missing (site admin)Group removal refusedReclaim fails although validation passed (validation does not test reclaim)Download activity clearedActivity job not created or deletedNo SAM - Refresh <name> 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.Alias set directly on the subflow in Flow DesignerScheduled job applies a second overrideCannot override connection alias. Flow jira_download_subscriptions already has an override configured for alias:<id>Default Jira group renamed or missing (older versions)Validation checks a group that no longer existsValidate Connection failsProfile edited after publishStatus returns to Draft, activity job removedJobs stop until validated and published againSubscription-identifier content out of dateIdentifier cannot mapEmpty software model; entries under Unrecognized Subscription IdentifiersNo matching sys_userSubscription user stays emptyReconciliation consumes no right; candidates go to Attention RequiredDebug properties left onExtra loggingSlow instance after troubleshooting Scopes by version (OAuth 2.0 only) ProcessSaaS License Management 17.4.0 and earlier17.4.1 and laterDownloadread:application-role:jira, read:group:jira, read:user:jira, read:avatar:jiraread:user:jira, read:group:jira, read:avatar:jiraActivityread:user:jira, read:issue-details:jira, read:audit-log:jira, read:avatar:jira, read:field-configuration:jira, read:issue-meta:jiraread:jira-user, read:audit-log:jira, read:jira-workReclaimread:group:jira, write:group:jiraread:group:jira, manage:jira-configuration 3. Symptoms and expected behavior SymptomFirst branchHealthy evidence to seekJira option, spoke or jobs missingAJira profile type available, jobs listedCannot publish, or profile back in DraftBStatus Published with its jobsValidate Connection failsCValidation successful401, wrong site, Basic auth problemsDGroup requests return 200OAuth consent fails, scopes, 403EToken present, validation passesJob runs but no usersFUsers returned for each selected group404 on /rest/api//group/memberGRequest path contains the API versionAlias override error, several Jira sitesHOne child alias and profile per siteRefresh job failedICompleted row in the job logFewer subscriptions than Jira showsJOne subscription per member of the selected groupsIdentifier or model problemsKAtlassian Jira Cloud model on every subscriptionUser empty or wrongLIntended sys_user linkedLast activity blank or staleMRecent activity for a user who created or commented on issuesActivity job errorsNActivity job completesNo reclamation candidatesOCandidate for a known inactive userReclaim fails or access remainsPUser removed from the selected groups429, timeouts, unreachable siteQNormal run durationProblems after clone, upgrade or repairRValidated profile, current versions A healthy download creates one subscription per user in the selected Jira groups, all under the single product Atlassian Jira Cloud. A user in several selected groups still has one subscription. 4. Execution path and evidence correlation Hover or tap a step to see what breaks there; click it to open the matching branch.SetupConnectionCollectionMatchingWriteDownstream Subscription downloaddaily 1Published profileJira Spoke, alias chosen by checkboxes, validatedBreaks here: Jira missing, no Publish, back in DraftOpen branch B →2Refresh jobSAM - Refresh <name> SubscriptionsBreaks here: Failed to download subscriptions; alias overrideOpen branch I →3CredentialBasic (email + API token) or OAuth 2.0 (3LO)Breaks here: 401 Unauthorized; consent error; 403Open branch D →4Site and API versionapi.atlassian.com/ex/jira/<Cloud-ID>, /rest/api/<version>Breaks here: 404 on /rest/api//group/memberOpen branch G →5Selected groupsJira Groups table, picker needs jira_adminBreaks here: Empty selection: zero users, no errorOpen branch F →6Group membersMembers of each selected group, pagedBreaks here: Users missing; unselected groupsOpen branch J →7ProductOne identifier JIRA_SOFTWARE for every groupBreaks here: Duplicate models, unrecognized identifierOpen branch K →8UserAtlassian email to sys_userBreaks here: Empty or wrong userOpen branch L →9Upsert and cleanupDeactivate, upsert, delete users not returnedBreaks here: Disappearing subscriptionsOpen branch J → Activity and reclaimdaily 1Activity jobSAM - Refresh <name> Activity after a good downloadBreaks here: Job missing; Download activity clearedOpen branch M →2Audit logSign-ins; Administer Jira permissionBreaks here: Blank activity; 403; truncated JSON propertyOpen branch M →3Issue searchCreated, commented, changed; page size 1-999Breaks here: Time zone, JQL or page size errorsOpen branch N →4Last activityLatest event, moves forward onlyBreaks here: Browsing does not countOpen branch M →5CandidatesRule per product, 60-day look-back defaultBreaks here: No candidatesOpen branch O →6ReclaimRemove the user from each selected groupBreaks here: Access remains via other groups; site admin neededOpen branch P →7After clone or upgradeCredentials re-entered, child aliases rebuiltBreaks here: Missing API version, missing buttonsOpen branch R → Subscription download path Subscriptions job → profile and Jira credential → selected groups (Jira Groups table) → members of each group (paged) → upsert under JIRA_SOFTWARE → delete users not returned → reclamation rules → usage summary → user resolution Activity and reclaim path Activity job (only after a good download) → look-back window → audit log (sign-ins) → issue search (created, commented, changed) → last activity moved forward → candidates → reclaim: remove the user from each selected group StageRecord or source to inspectBehaviorJobsProfile > Scheduled JobsCreated on publish: a subscriptions job, plus an activity job when Download activity is selectedJob resultProfile > Scheduled Job Results (sam_saas_job_log) and the red banner on the profileStatus and message of each runConcurrencysys_triggerA second run stops with An instance of '<job>' is already running. Please wait till it completes in the system log and writes no job resultConnectionAlias and child aliasBasic (email and API token) through api.atlassian.com, or OAuth 2.0; the API Version attribute builds the request pathGroupsTable sn_jira_spoke_jira_groupsOnly the groups selected for the connection are read; empty selection means zero usersMembersLook up Users by Group Name StreamGroup members are paged; each user's Atlassian account ID is the keyUpsertsamp_sw_subscriptionOne subscription per user, identifier JIRA_SOFTWARECleanupProfile subscriptionsRows are deactivated before the pull; rows not returned are deleted; on failure active flags are restoredActivityAudit log and issue searchLooks back from the last event sync (default 60 days); the audit log records sign-ins, and issues contribute create, comment and change activityTime zoneJira authenticated userThe look-back time is converted to the time zone of the Jira user before it is used in the searchReclaimJira Reclaim SubscriptionRemoves the user from each selected group the user belongs to; the Jira account is not deactivated Correlate one execution before deciding a cause Record the job, profile, start and end in UTC, and the versions of SaaS License Management and the Jira Spoke.Open the profile's Scheduled Job Results (sam_saas_job_log) and read the message.Open Flow Designer > Executions for Jira Download Subscriptions (and its child Jira Look up Group Members) or Jira Update User Activity, and find the failing step.Open System Logs > Outbound HTTP Requests filtered on URL contains atlassian; 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 <name>, <id> or <Cloud-ID> are placeholders; keep the real values private. Start every investigation here 1Job resultProfile > Scheduled Job Results (sam_saas_job_log)Status and message; red banner on the profile 2Flow executionFlow Designer > Executions, Jira subflowThe exact step and error 3Outbound HTTPURL contains atlassianStatus, path (note /api//) and Atlassian error body 4Pick a branchMatch the message below401 → D, consent → E, zero users → F, /api// → G, override → H 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 Jira subflow at the same time. (3) System Logs > Outbound HTTP Requests with URL containing atlassian. Read the response body, not only the status code. A. Jira option, spoke, subflows or jobs are missingB. The profile cannot be published, or returns to DraftC. Validate Connection failsD. Basic authentication fails (401, wrong site)E. OAuth 2.0 consent fails, scopes or 403F. The job runs but no users are importedG. API version missing, HTTP 404 on group requestsH. Alias override error, or several Jira sitesI. The refresh job failsJ. Fewer subscriptions than Jira showsK. Identifier or software model problemsL. Subscription user is empty or wrongM. Last activity is blank or staleN. Activity job errorsO. No reclamation candidates for JiraP. Reclaim fails, or access remains after reclaimQ. Rate limits, timeouts or an unreachable siteR. Problems after a clone, upgrade or repair A. Jira option, spoke, subflows or jobs are missingThis action's definition is missing Symptoms. Jira is not offered when creating a direct integration profile.Jira subflows are missing in Flow Designer, or a subflow step shows This action's definition is missing.No SAM - Refresh <name> Subscriptions job after publishing. Where to check. Application Manager > SaaS License Management > optional features; installed applications for the Jira 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 Jira Spoke (Confluence has its own Confluence Cloud Spoke option).Core UI create option inactive. With Software Asset Workspace installed, create the profile from License operations > User subscriptions > Direct integration profiles > New > Jira.Integration Hub missing. Confirm the Integration Hub subscription.Missing action definitions. Update SaaS License Management and the Jira Spoke together.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 published, or returns to DraftApplication is set to <scope> scope. Switch to 'Global' application scope to publish this integration profile. Symptoms. No Publish button.Application is set to <scope> scope. Switch to 'Global' application scope to publish this integration profile.A published profile is back in Draft and its jobs stopped.The profile appears to use a different credential than the one selected. Where to check. Profile form (Status, subflow checkboxes, Connection & Credential); the alias; Scheduled Jobs. Causes and fixes. Not validated. Publish appears only after Validate Connection succeeds (C).Wrong scope. Switch to the Global application scope and publish.Alias selected by the checkboxes. The alias is chosen on Save from the ticked processes (section 2). If you change the Download activity or Reclaim subscriptions checkboxes after publishing, the profile returns to Draft, the Validate button reappears and the activity job is removed. Validate and publish again.Connection changed without re-validation. After switching to a child alias or recreating a connection, validate and publish again even if the status still shows Published.Older versions ignored the selected alias. Update SaaS License Management, then select the alias again and validate. Verify. Status Published; the subscriptions job and, if selected, the activity job listed. C. Validate Connection failsConnection validation is not successful. Please check connections and credentials and try again.Connection validation is not successful. Invalid inputs passed to action. Please check the action.Page Size should be in range 1-999JQL Query cannot be empty. Symptoms. Connection validation is not successful. Please check connections and credentials and try again.Connection validation is not successful. Invalid inputs passed to action. Please check the action.HTTP 400 from Atlassian with authorized true in the response while validating.Page Size should be in range 1-999 or JQL Query cannot be empty.Validation fails although a token was obtained. Where to check. Flow Designer execution of the validation; the outbound log; the profile's Analyze user activity from date and the validating user's date format. Causes and fixes. What validation tests. It lists groups and the members of the first group; with Download activity selected it reads the audit log and runs an issue search. It does not test reclaim, so a pass does not prove reclaim works.Date format. The activity check builds a date for the issue search from the profile's activity start (yyyy-MM-dd HH:mm). A related validation problem with non-ISO date formats is confirmed for Confluence; it is not confirmed for Jira. If validation returns HTTP 400 while authorization is fine, set the validating user's and instance date format to yyyy-MM-dd, validate again, and update SaaS License Management. An HTTP 400 with authorization true is a request problem, not a credential problem.No groups selected. The group check needs at least one selected group (F).Default group renamed or missing (older versions). Validation checked a default group; keep the group as shipped or make sure the configured group exists in Jira, and update the application.Token obtained but validation fails (older versions). Update SaaS License Management and validate again.Activity inputs. The page size must be between 1 and 999 and the issue query cannot be empty; if you see these messages, the activity settings on the profile are blank or invalid; reopen the profile and save the activity options.Credentials, scopes or permissions. See D and E.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. Basic authentication fails (401, wrong site)Unauthorized - Incorrect username and / or password.Could not authenticate the request. Symptoms. Unauthorized - Incorrect username and / or password.Could not authenticate the request.HTTP 401 or 404 from api.atlassian.com, or an HTML page instead of JSON. Where to check. The connection record (Connection URL, User Name, API Key); the Atlassian account; the outbound response body. Causes and fixes. Wrong or revoked API token. Create a new token on the Atlassian account's API tokens page, copy it once, and paste it in the connection's API Key field; validate.Wrong email. User Name must be the account's email address.Wrong Cloud ID or URL. The Connection URL must be https://api.atlassian.com/ex/jira/<Cloud-ID>; take the Cloud ID from Atlassian Administration (Apps > Atlassian apps > Manage app on the Jira row). One Cloud ID is one site.Account lacks Jira permissions. The account needs the permissions for each process (section 2).Token rotation. Create the new token, update the connection, validate and run the job, then remove the old token. Verify. The group request returns 200 and validation succeeds. E. OAuth 2.0 consent fails, scopes or 403Hmm, we're having trouble connecting you. ... It looks like the problem is with your identity provider. Wait a few moments, then Try again.Missing required parameter: scope Symptoms. Atlassian page: Hmm, we're having trouble connecting you. ... It looks like the problem is with your identity provider. Wait a few moments, then Try again.HTTP 403 from the group, audit-log or issue calls.Missing required parameter: scope when fetching the token. Where to check. System OAuth > Application Registry (Jira); the OAuth entity profile and its scope records; the Atlassian developer console app (17.4.0 and earlier). Causes and fixes. Setup by version. In 17.4.0 and earlier create an OAuth 2.0 (3LO) app in the Atlassian developer console with the callback URL https://<your-instance>.service-now.com/oauth_redirect.do and the scopes in section 2, copy Client ID and Secret into the connection, then Create and Get OAuth Token and consent. In 17.4.1 and later the Client ID, Secret and Redirect fields no longer appear on the connection dialog; enter the Cloud ID directly.OAuthUtilSAM in the OAuth API Script field. Remove it from the Jira entry in the Application Registry.No scope records. Add the scope records to the OAuth entity profile (and populate the Scope field if the token request reports it missing).Callback URL typo. Correct the callback URL in the Atlassian app to match your instance.403 after a token was issued. The token works but Jira refuses the request: the authorizing user lacks the permission, the app lacks a scope, or an admin policy or IP allow list blocks it. A new token does not fix this. Fix the permission, scope or policy and authorize again from the alias's OAuth 2.0 credential record (Get OAuth Token).After an upgrade. Scopes differ between 17.4.0 and 17.4.1; re-check the scopes after moving versions. Verify. A token is returned and validation succeeds. F. The job runs but no users are imported Symptoms. Job Completed with zero subscriptions and no error; the group picker shows no groups; only some groups' users appear. Where to check. Jira > Jira Groups (table sn_jira_spoke_jira_groups) and its Add Groups related link; the user's roles; the flow execution's group step. Causes and fixes. No groups selected. Only users in selected groups are retrieved and managed. Open Jira > Jira Groups, use Add Groups, choose the same Connection & Credential as the profile, and move the groups that grant Jira product access from Available to Selected. An empty selection imports nothing and raises no error.Picker shows nothing. The group picker works only for users with sn_jira_spoke.jira_admin; grant the role.Wrong connection. Groups are stored per connection; selecting groups under another connection leaves this profile empty.Users not in selected groups. Users with access through an unselected group have no subscription; add the group.Whole directory imported (older versions). Older versions pulled all users instead of the selected groups; update the application and confirm the selected groups. Verify. The flow execution shows each selected group with its members and subscriptions appear. G. API version missing, HTTP 404 on group requestsFailed to iterate on data streamJSON must be an object or an array: '<'Invalid Resource path, please verify API Version in the Connection Attributes of the Connection Alias used. Symptoms. Job fails with Failed to iterate on data stream and JSON must be an object or an array: '<'.Outbound log: 404 on https://<site>.atlassian.net/rest/api//group/member?groupname=<group>&includeInactiveUsers=false&startAt=0&maxResults=50 (a double slash after api).Invalid Resource path, please verify API Version in the Connection Attributes of the Connection Alias used. Where to check. The parent alias's Connection Attributes; the child alias's connection record; the outbound URL. Causes and fixes. Child alias lost the API Version attribute. This happens typically on an imported or cloned child alias that did not inherit the parent's attributes. Open the parent alias (sn_jira_spoke.Jira) and confirm the API Version attribute exists; delete the broken child; create the child again from the parent's Child Aliases tab so the attributes are added; or add the API Version attribute directly on the HTTP connection.Spoke damaged. If the attribute is missing on the parent too, repair the Jira Spoke.HTML in place of JSON. The < is the start of Atlassian's 404 page; it confirms the path is wrong rather than the credentials. Verify. The outbound URL reads /rest/api/<version>/group/member..., the job completes and subscriptions appear. H. Alias override error, or several Jira sitesCannot override connection alias. Flow jira_download_subscriptions already has an override configured for alias:<id> Symptoms. Cannot override connection alias. Flow jira_download_subscriptions already has an override configured for alias:<id>The second profile shows the first site's users; New is missing on the Child Aliases tab. Where to check. Flow Designer > the Jira subflows > Configure Connections; the parent alias. Causes and fixes. Override set on the subflow. Someone set a connection directly on the subflow, and the scheduled job also applies the profile's alias. Open Jira Download Subscriptions and every nested subflow, open Configure Connections, reset the Jira alias to Use Default Connection, and set the alias only on the integration profile. Running the subflow manually works while the scheduled job fails.One profile per site. Create the profile; on the parent alias sn_jira_spoke.Jira set the Configuration template to match the ticked processes (for example Jira Subscription Activity and Reclaim); save, open Child Aliases > New (switch to the Jira Spoke application scope if New is missing), submit the child, create a connection and credential on it, select the child alias on the profile, save and publish.Groups per connection. Select the groups again for each child connection (F).Child alias ignored (older versions). Update SaaS License Management. Verify. The scheduled job runs without the override error and each profile imports only its own site's users. I. The refresh job failsFailed to download subscriptions.Failed to calculate last activity.You must add integration_profile and look_back_time as inputs.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] Symptoms. Scheduled Job Results shows Failed with: Failed to download subscriptions.Failed to calculate last activity.You must add integration_profile and look_back_time as inputs.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' Where to check. The job result message; the failing step in the Flow Designer execution; the outbound log. Causes and fixes. Underlying Jira error. The messages are summaries; open the flow execution and fix the step error (D, E, G, N, Q).Outdated application or spoke. Update SaaS License Management and the Jira 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; some subscriptions can miss their activity stamp in older versions. Verify. The next run shows Completed and updated subscriptions. J. Fewer subscriptions than Jira shows Symptoms. Users missing; counts do not match the Atlassian admin console; users disappear after a run. Where to check. Selected groups; the member requests for each group; exclusion rules on the profile. Causes and fixes. Group selection. Only members of the selected groups are counted (F).User not in a product group. A user with Jira access through a group that is not selected is missing.One subscription type. All selected groups map to the single product Atlassian Jira Cloud; seats of Jira Service Management or Work Management are not separated.Exclusion rules. Subscription Identifier Exclusion Rule and Subscription User Exclusion Rule silently drop matching rows. Review both related lists.Failed run. A failed run restores active flags but does not undo deletions already made; fix the cause and rerun.Users removed from groups in Jira. They lose their subscription at the next pull. Verify. Counts match the members of the selected groups, and a previously missing user appears after the next run. K. Identifier or software model problems Symptoms. A raw identifier and no software model; several Jira models for the same product; entries under Unrecognized Subscription Identifiers. Where to check. Profile > Software Models and Unrecognized Subscription Identifiers; content download status. Causes and fixes. Content out of date. Download current subscription-identifier content; the integration produces one identifier, JIRA_SOFTWARE, mapped to the Atlassian Jira Cloud model.Unknown identifier. Open it under Unrecognized Subscription Identifiers, set the correct software model and save.Duplicate models (older versions). Update the application, then clean up duplicate Jira models and normalize names.Missing model on some subscriptions. Run the content update and rerun the refresh job. Verify. Every subscription shows the Atlassian Jira Cloud model. L. Subscription user is empty or wrong Symptoms. Subscriptions with an identifier but no User; records on the Subscriptions without user page; last activity not updated for a matched user. Where to check. sys_user email and user ID versus the Atlassian account email; User resolution rules; sn_itam_samp.user_resolution_exclude_table. Causes and fixes. No match. The Atlassian account's email (user principal name) is matched to sys_user Email, or its local part to User ID. A mismatch also blocks last activity. 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 (comma-separated).Rules that run a script (older versions). Update SaaS License Management if a script-based rule does not resolve users.Manual edits overwritten. The User field is recalculated each run. Verify. The subscription shows the intended user. M. Last activity is blank or stale Symptoms. Jira subscriptions have no last activity, or it does not match what Jira shows; users who only browse have none. Where to check. The activity job result; the audit-log and issue-search requests; the user's recent Jira actions. Causes and fixes. What counts as activity. Only sign-ins (audit log) and issue activity count: user login, creating an issue, commenting and updating a comment, plus changes recorded on issues. Viewing issues or browsing does not count, so such users legitimately show no activity.Activity job missing. Select Download activity, validate and publish; the job SAM - Refresh <name> Activity is created.Download not healthy. The activity job runs after a good subscriptions run (I).Permissions. The account needs Administer Jira, Browse Projects and, where issue security applies, permission to view the issue; scopes in section 2 (E).Required property. Make sure com.glide.transform.json.max-partial-length is 32768; without it large responses are truncated and the activity subflow fails.Anonymous or deleted users. Activity entries without an Atlassian account ID or timestamp are dropped.Look-back. Activity is read from the last sync or Analyze user activity from (default 60 days).Never cleared. Last activity only moves forward. Verify. A user who created or commented on an issue today shows today's date after the next activity run. N. Activity job errorsError in JiraActivity.formatDateForJqlQuery: <error>JiraActivity.formatDateForJqlQuery received invalid datetime: <value>Page Size should be in range 1-999JQL Query cannot be empty.Account Id cannot be empty for cloud. Symptoms. Error in JiraActivity.formatDateForJqlQuery: <error>JiraActivity.formatDateForJqlQuery received invalid datetime: <value>Page Size should be in range 1-999JQL Query cannot be empty.Account Id cannot be empty for cloud. Where to check. The activity subflow execution; the profile's activity settings. Causes and fixes. Time zone lookup failed. The look-back time is converted to the time zone of the Jira user through the authenticated-user request; if that call fails or returns nothing, the date conversion fails. Fix the authentication error (D, E) and rerun.Invalid date. The look-back value is not a valid date; correct Analyze user activity from on the profile.Page size or query blank. Reopen the profile, save the activity options and validate.Missing account ID. A user lookup for Jira Cloud needs the Atlassian account ID; users without one cannot be processed.Truncated responses. Check the required property (M5). Verify. The activity job completes and last activity updates. O. No reclamation candidates for Jira Symptoms. Inactive users get no removal candidate. Where to check. The Jira reclamation rule; subscriptions' user and last activity; existing candidates. Causes and fixes. Last activity blank. Candidates depend on activity; fix M first.Rule configuration. Confirm Create reclamation candidate is checked, the Last activity threshold is set and the subscription condition matches. Rules are created automatically per product on download.User empty. With Notify user on, a candidate without a user goes to Attention Required; fix L.Candidate states. Attention Required, Ready, Awaiting User, Awaiting Approval, Awaiting Revocation, Closed Complete, Closed Skipped, Closed Canceled (cancelled when activity is detected). Integrations with write-back are removed automatically; otherwise the SAM administrator removes the access manually. Verify. A known user inactive beyond the threshold receives one candidate. P. Reclaim fails, or access remains after reclaimThe reclamation of user subscriptions will not be successful because the Reclaim subscription checkbox isn't selected on the integration profile.Failed to reclaim subscription.Username cannot be empty for server.Account Id cannot be empty for cloud. Symptoms. The reclamation of user subscriptions will not be successful because the Reclaim subscription checkbox isn't selected on the integration profile.Failed to reclaim subscription.Username cannot be empty for server. or Account Id cannot be empty for cloud.The user still has Jira access after the candidate closed. Where to check. The candidate's banner; the Jira Reclaim Subscription flow execution; the outbound request; the Jira account's groups. Causes and fixes. What reclaim does. It removes the user from each selected group the user belongs to. It does not deactivate the Jira account and does not remove product access directly. A user who keeps access through another group that is not selected still has access.Reclaim not configured. Select Reclaim subscriptions, validate and publish.Not covered by validation. Test reclaim with one candidate.Permissions. Reclaim needs a site administrator (member of the site-admin group) and, for OAuth, the reclaim scopes (section 2). A 401 or 403 here points to the account or scope.Missing account ID. A removal needs the Atlassian account ID; rerun the download so it is populated.Access via other groups. Add the other access-granting groups to the selection (F) so reclaim and counting cover them. Verify. The user is no longer in the selected groups, the candidate closes and the subscription is removed on the next run. Q. Rate limits, timeouts or an unreachable siteRate limit exceeded.Request to the Jira cloud instance timed out.Either the URL to the Jira Cloud instance is incorrect or the server is unreachable or down.URL is Invalid.One or more of the inputs are Invalid. Symptoms. Rate limit exceeded.Request to the Jira cloud instance timed out.Either the URL to the Jira Cloud instance is incorrect or the server is unreachable or down.URL is Invalid.One or more of the inputs are Invalid. Where to check. The outbound log status and body; the connection URL; job duration. Causes and fixes. Rate limit. Atlassian returned HTTP 429; avoid manual runs near scheduled runs and do not run the subscriptions and activity jobs at the same time. A daily limit message can also appear on large runs; wait for the limit to reset and update the application.Timeouts. Large sites take longer; keep the Analyze user activity from window reasonable and rerun.Unreachable site (503). Check the Connection URL and Atlassian status, and that the instance can reach api.atlassian.com.Invalid URL or inputs. Re-enter the connection URL and check the action inputs.Flow reporting overhead. Keep com.snc.process_flow.reporting.level at OFF in production. Verify. A complete run without unhandled 429 or timeouts. R. Problems after a clone, upgrade or repair Symptoms. Profile form missing fields; Validate or Publish missing after an upgrade; tokens fail after a clone; imported child aliases fail (G). Where to check. Installed versions; customizations of SaaS License Management; the profile's connection; 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.Validate missing after an upgrade. The upgrade fix script that enables Validate Connection on existing profiles runs as a scheduled job; check sys_trigger and let it finish.Credentials after a clone. Credentials and tokens are instance-specific; re-enter the API token (or reauthorize) and validate. Imported or cloned child aliases can lose their attributes (G).Scopes after moving to 17.4.1 or later. Re-check the scopes (section 2).Versions out of step. Update SaaS License Management and the Jira Spoke together. 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, spoke or profile typeServiceNow platform administratorInstall or update, validate, publishAtlassian token, account or permissionsJira site administrator and integration ownerFix the credential or permission, validate, run onceGroups not selectedSAM integration owner with a Jira administratorSelect the access-granting groups, run once, compare countsAPI version or aliasSAM integration ownerRecreate the child alias or add the attribute, validateMapping or user resolutionSAM administratorMap identifiers or add rules, rerunActivitySAM integration ownerEnable activity, set the property, run onceReclaimSAM process owner and Jira site administratorReclaim one candidate first; confirm other access groupsClone, upgrade, repairPlatform ownerRestore out-of-box components, re-enter credentials, validate, run once 7. Verification criteria and recovery evidence Verification layerEvidence requiredWhat does not satisfy itConfigurationPublished profile, valid credential, API Version on the connection, groups selectedA Published status after an unvalidated connection changeExecutionCompleted sam_saas_job_log row and a successful flow executionA scheduled job that existsCoverageSubscriptions match members of the selected groupsTotal counts that ignore unselected groupsMatchingModel and user on every subscriptionRaw identifiers as display namesActivityRecent last activity for a user who created or commented on an issueBlank activity read as inactivityReclaimOne reclaimed user removed from the selected groups in JiraCandidate closed without the Jira change 8. Escalation evidence to collect Versions of SaaS License Management, the Jira Spoke and the platform; recent upgrades, repairs or clones.Authentication type (Basic or OAuth), alias or child alias, number of Jira sites, number of selected groups.Profile status and selected options.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 site replaced by a placeholder, status and the Atlassian error body (no tokens).Counts of members in the selected groups and subscriptions in ServiceNow; one missing user's group membership (no names).Steps already taken and results. Never include API tokens, client secrets or user names in shared evidence. 9. References, processing rules and known limitations Key records Jobs: SAM - Refresh <name> Subscriptions, SAM - Refresh <name> Activity.Subflows: Jira Download Subscriptions (child Jira Look up Group Members), Jira Update User Activity, Jira Reclaim Subscription.Spoke: alias sn_jira_spoke.Jira and child aliases; group table sn_jira_spoke_jira_groups; role sn_jira_spoke.jira_admin.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 com.glide.transform.json.max-partial-length — must be 32768 for the activity subflow.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 Only members of the selected groups are imported; an empty selection imports nothing without an error.All selected groups map to one product, JIRA_SOFTWARE.Users are keyed by their Atlassian account ID; the email is matched to sys_user.Each download deactivates rows, upserts, and deletes users not returned.Activity is sign-ins and issue activity inside the look-back window; browsing does not count.Reclaim removes the user from the selected groups; the Jira account stays active.Validation covers download and activity, not reclaim. Known limitations Jira Service Management, Work Management and Data Center seats are not modeled separately.Only sign-ins, issue creation, comments and recorded issue changes count as activity.Atlassian rate limits depend on your Atlassian plan and are not documented here. Documentation ServiceNow product documentation for your release: Integrate with Jira under Software Asset Management > SaaS License Management.Atlassian developer documentation: API tokens, OAuth 2.0 (3LO) and Jira Cloud REST API scopes.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 Jira 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 Jira account 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 Jira 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 Jira 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 L)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 Jira account email has no unique exact match in any sys_user fieldCorrect user data or create the rule manually (branch L) 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.