Troubleshooting ServiceNow SAM Confluence Cloud 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 Confluence Cloud 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 Confluence Cloud direct integration profile (profile type confluence_cloud_subscription, label Confluence Cloud Subscription). It runs on the SaaS License Management subflow framework: the profile's subflows call the Confluence Cloud Spoke, whose scope is spelled sn_conflunce_spoke in the product, and read Confluence 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 Confluence groups you select on the connection are imported, and every selected group maps to the same product, Atlassian Confluence Cloud (identifier CONFLUENCE_CLOUD). Reclaim removes a user from groups; it does not deactivate the Atlassian account. Cloud only, one site per profile. The integration supports Confluence Cloud only, and one Atlassian site per profile. Support for several sites in one profile is a product limitation; use one profile (and one child alias) per site. It shares its Atlassian setup with the Jira Software Cloud integration (a separate article). It does not cover Confluence in ServiceNow AI Search or knowledge connectors, 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 Confluence Cloud Spoke. Setup differs 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 Confluence Cloud SpokeInstalled and currentIntegration HubSubscription and plugins com.glide.hub.integration.runtime, com.glide.hub.action_step.rest, com.glide.hub.action_type.datastreamActiveRoles (ServiceNow)User creating the profile and using the group pickersam_integrator, and sn_conflunce_spoke.confluence_cloud_admin for the group picker and site lookupAtlassian roleAtlassian administrationSite admin to create the profileAtlassian permissionsAtlassianDownload and activity: a product user role; reclaim: site adminCloud IDAtlassian Administration > organization > Products > Manage product on the Confluence rowThe Cloud ID is the last part of that page's address (.../products/conf/<Cloud-ID>)Connection URLConnection recordhttps://api.atlassian.com/ex/confluence/<Cloud-ID> (the host must be api.atlassian.com)OAuth app (17.4.0 and earlier)Atlassian developer console > Create app > OAuth 2.0 (3LO)Callback URL https://<your-instance>.service-now.com/oauth_redirect.do; Confluence API permissions added with the scopes below; Client ID and secret copiedOAuth app (17.4.1 and later)Connection dialogNo Client ID, secret or redirect fields; the Atlassian app is not created by youProfileSoftware Asset Workspace > License operations > User subscriptions > Direct integration profiles > New > Confluence CloudDownload subscriptions (locked on), Download activity (default on), Reclaim subscriptions (default on)AliasProfile Connection & CredentialChosen on Save by the checkboxes: sn_conflunce_spoke.confluence_subscription_activity_reclaim (both), ...confluence_subscription_activity, ...confluence_subscription_reclaim, or ...confluence_subscriptionAuthorizationAlias > Create New Connection & Credential > Create and Get OAuth TokenAtlassian consent screen allowed by a site administratorConfluence groupsConfluence Cloud > Confluence Groups > Add GroupsThe groups that grant Confluence access moved to Selected, using the profile's Connection & CredentialValidation 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 duplicatesDate formatSystem Properties and the validating userglide.sys.date_format is yyyy-MM-dd (see C) Scopes ProcessAtlassian scopesDownload subscriptionsread:confluence-groups, read:confluence-userPull user activitysearch:confluenceReclaim subscriptionsread:confluence-groups, write:confluence-groups In the Atlassian developer console (17.4.0 and earlier) these appear as: Search Confluence content and space summaries, Read user groups, Create, remove and update user groups, and Read user. On Australia and later the OAuth app must carry the scopes each flow needs; re-authorize after adding scopes. What happens when a setting is missing or wrong Setting, field or propertyIf it is missing or wrongTypical symptomConfluence Cloud Spoke not selected as an optional featureProfile type and subflows missingConfluence Cloud is missing from New on Direct integration profilesUser without sn_conflunce_spoke.confluence_cloud_adminGroup picker and site lookup return nothingCannot select groups; Site ID cannot be retrieved. Check with your administratorNo groups selectedDownload iterates over nothingJob completes with zero users and no errorConnection URL host not api.atlassian.comThe profile cannot be saved or the call goes to the wrong hostConnection validation or publish errorsAtlassian account with MFA that needs interactive approvalToken refresh fails after the token expires{"error":"unauthorized_client","error_description":"refresh_token is invalid"}Authorizing user has no access to the Confluence siteThe site cannot be resolvedSite ID cannot be retrieved. Check with your administrator and then API errors for /ex/confluence/undefined/wikisearch:confluence scope missingActivity search refusedActivity job fails while the subscription download succeedswrite:confluence-groups scope or site-admin role missingGroup removal refusedReclaim fails although validation passed (validation does not test reclaim)glide.sys.date_format not yyyy-MM-ddValidation builds an invalid CQL dateCould not parse cql : with HTTP 400 and authorized trueOAuthUtilSAM in the OAuth API Script field of the Confluence entryAtlassian refuses the consentHmm, we're having trouble connecting you.OAuth entity profile has no scope recordsConsent screen cannot be builtThe same Atlassian messageCallback URL typo in the Atlassian appCallback failsThe same Atlassian messageDownload 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.Profile edited after publishStatus returns to DraftJobs stop until validated and published againAtlassian privacy settings hide the emailMember email is emptySubscription user cannot be resolvedSpoke or application out of dateRequired actions or fixes missingThis action's definition is missing, wrong last activity, reclaim problemsDebug properties left onExtra loggingSlow instance after troubleshooting 3. Symptoms and expected behavior SymptomFirst branchHealthy evidence to seekConfluence option, spoke or jobs missingAProfile type available, jobs listedCannot publish, or profile back in DraftBStatus Published with its jobsValidate Connection failsCValidation successfulAtlassian consent or scope errorsDToken present with the right scopesToken expired, Site ID cannot be retrievedEAccessible-resources request returns 200Wrong site, Cloud ID or URLFRequests go to /ex/confluence/<Cloud-ID>Job runs but no usersGUsers returned for each selected groupSeveral Confluence sitesHOne profile and child alias per siteRefresh job failedICompleted row in the job logToo many or too few subscriptionsJOne subscription per licensed member of the selected groupsIdentifier or model problemsKAtlassian Confluence Cloud model on every subscriptionUser empty or wrongLIntended sys_user linkedLast activity blank or staleMRecent activity for a user who edited contentActivity job errorsNActivity job completesNo reclamation candidatesOCandidate for a known inactive userReclaim fails or access remainsPUser removed from the selected groupsLimits, paging, timeoutsQNormal run durationProblems after clone, upgrade or repairRValidated profile, current versions and scopes A healthy download creates one subscription per user in the selected groups, all under the single product Atlassian Confluence 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 profileConfluence Cloud Spoke, alias chosen by checkboxes, validatedBreaks here: Option missing, no Publish, back in DraftOpen branch B →2Refresh jobSAM - Refresh <name> SubscriptionsBreaks here: Failed to download subscriptions; alias overrideOpen branch I →3OAuth consentAtlassian 3LO; scopes by versionBreaks here: Trouble connecting you; missing scopeOpen branch D →4Token and site IDAccessible resources unless URL has /ex/confluenceBreaks here: Site ID cannot be retrieved; refresh_token invalidOpen branch E →5Cloud ID and URLapi.atlassian.com/ex/confluence/<Cloud-ID>Breaks here: Wrong site; HTTP 404Open branch F →6Selected groupsConfluence Groups table; picker needs the admin roleBreaks here: Empty selection: zero users, no errorOpen branch G →7Group membersActive members, 200 per pageBreaks here: Unlicensed or deactivated accounts importedOpen branch J →8Product and userCONFLUENCE_CLOUD; email to sys_userBreaks here: Email hidden; empty 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 →2Content searchCQL lastmodified since the activity start, 200 per pageBreaks here: Could not parse cql; date formatOpen branch C →3Last activityLast updater of each item, UTC, moves forward onlyBreaks here: Reading does not countOpen branch M →4Update eventsAttachment, space, comment, blog post, pageBreaks here: No events recordedOpen branch M →5CandidatesRule per product, last activity thresholdBreaks here: No candidatesOpen branch O →6ReclaimRemove the user from each selected groupBreaks here: Access via other groups; site admin and write scopeOpen branch P →7After clone or upgradeToken re-authorized, scopes re-checkedBreaks here: Missing buttons, scope errorsOpen branch R → Subscription download path Subscriptions job → profile and Atlassian token → site ID (accessible resources, unless the URL already contains /ex/confluence) → selected groups (Confluence Groups table) → members of each group (200 per page) → upsert under CONFLUENCE_CLOUD → delete users not returned → reclamation rules → usage summary → user resolution Activity and reclaim path Activity job (only after a good download) → look-back window → Search Content (CQL lastmodified from the activity start date, 200 results per page, history.lastUpdated expanded) → last activity moved forward for the person who last updated each item → update events → candidates → reclaim: remove the user from the selected groups 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 resultSite IDLook up Accessible ResourcesIf the connection URL has no /ex/confluence part, the integration reads the sites granted to the token and uses the last one whose scopes include ConfluenceGroupsTable sn_conflunce_spoke_confluence_groupsOnly the selected groups are read; each row is stored per connection; empty selection means zero usersMembersLook up Members By Group IDActive members of each group, with account ID, email, display name and account typeUpsertsamp_sw_subscriptionOne subscription per user, identifier CONFLUENCE_CLOUDCleanupProfile subscriptionsRows are deactivated before the pull; rows not returned are deleted; on failure active flags are restoredActivitySearch ContentGET /wiki/rest/api/content/search with a CQL query; the item's last-updated person and time feed last activity; dates are UTCEventssamp_saas_feature_usageUpdated attachment, space, comment, blog post or pageReclaimRemove Member From Group By Group IDDELETE /wiki/rest/api/group/userByGroupId for each selected group the user belongs to; the Atlassian account stays active 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 Confluence Cloud Spoke.Open the profile's Scheduled Job Results (sam_saas_job_log) and read the message.Open Flow Designer > Executions for Confluence Cloud Download Subscriptions (child Confluence Cloud Look up Group Members) or Confluence Cloud Update User Activity, and find the failing step.Open System Logs > Outbound HTTP Requests filtered on URL contains atlassian; read status and response body. The Confluence spoke does not translate most Atlassian errors, so the body shown there is the real error.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, Confluence subflowThe exact step and error 3Outbound HTTPURL contains atlassianStatus and the Atlassian error body (the spoke does not translate it) 4Pick a branchMatch the message belowCould not parse cql → C, consent → D, Site ID → E, zero users → G 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 Confluence 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. Confluence option, spoke, subflows or jobs are missingB. The profile cannot be published, or returns to DraftC. Validate Connection failsD. Atlassian consent or scope errorsE. Token expired or the site ID cannot be retrievedF. Wrong site, Cloud ID or connection URLG. The job runs but no users are importedH. Several Confluence sites, child aliases and alias errorsI. The refresh job failsJ. Too many or too few subscriptionsK. Identifier or software model problemsL. Subscription user is empty or wrongM. Last activity is blank or staleN. Activity job errorsO. No reclamation candidates for ConfluenceP. Reclaim fails, or access remains after reclaimQ. Limits, paging and timeoutsR. Problems after a clone, upgrade or repair A. Confluence option, spoke, subflows or jobs are missingThis action's definition is missing Symptoms. Confluence Cloud is not offered when creating a direct integration profile.Confluence subflows are missing in Flow Designer, or a 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 Confluence Cloud 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 Confluence Cloud Spoke.Integration Hub missing. Confirm the Integration Hub subscription and the three Integration Hub plugins listed in section 2.Core UI create option inactive. With Software Asset Workspace installed, create the profile from License operations > User subscriptions > Direct integration profiles > New > Confluence Cloud.Missing action definitions. Update SaaS License Management and the Confluence Cloud Spoke together; a mismatched spoke version causes this.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 Draft Symptoms. No Publish button.The profile appears to use an older alias or ignores the selected alias.A published profile is back in Draft and its jobs stopped. 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).Alias follows the checkboxes. The alias is chosen on Save from the ticked processes (section 2). If you change Download activity or Reclaim subscriptions after publishing, the profile returns to Draft, the Validate button reappears and the activity job is removed; the alias then no longer matches your connection record, so create the connection again under the new alias, validate and publish.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, select the alias again and validate.Form fields missing on creation (older versions). Update SaaS License Management. Verify. Status Published; the subscriptions job and, if selected, the activity job listed. C. Validate Connection fails{"statusCode":400,"data":{"authorized":true,"valid":true,"errors":[],"successful":true},"message":"com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : "}Connection validation failed. Verify the configurations you have provided and then retry.Connection validation failed. Insufficient scopes provided. Verify the configurations you have provided and then retry.Connection validation is not successful. Invalid inputs passed to action. Please check the action. Symptoms. {"statusCode":400,"data":{"authorized":true,"valid":true,"errors":[],"successful":true},"message":"com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : "}Connection validation failed. Verify the configurations you have provided and then retry.Connection validation failed. Insufficient scopes provided. Verify the configurations you have provided and then retry.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 (URL, status, body); glide.sys.date_format. Causes and fixes. Date format. The activity check builds a search query from the profile's activity start date using the date part only (lastmodified>=yyyy-MM-dd). If glide.sys.date_format is not yyyy-MM-dd, Confluence returns HTTP 400 Could not parse cql. authorized is true, so authentication is fine; do not chase credentials. Set the date format back to yyyy-MM-dd for the validating user and instance, validate again, and update SaaS License Management for the permanent fix.The UI message is generic. Confluence errors (including CQL errors) collapse into the two generic validation messages, so read the response body in the outbound log for the real cause.What validation tests. It lists groups, reads the members of the first group and, with Download activity selected, runs a content search. It does not test reclaim, so a pass does not prove reclaim works.No groups. The members check uses the first group returned; with no groups, validation cannot run (G).Scopes or token. See D and E.Ambiguous dates in activity (older spoke versions). Update the Confluence Cloud Spoke to v1.2.6 or later.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. Atlassian consent or scope errorsHmm, we're having trouble connecting you. ... It looks like the problem is with your identity provider. Wait a few moments, then Try again. 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.A scope error when getting the OAuth token (older Xanadu releases).The token works for groups but not for activity or reclaim. Where to check. System OAuth > Application Registry (Confluence); the OAuth entity profile and its scope records; the Atlassian developer console app (17.4.0 and earlier). Causes and fixes. OAuthUtilSAM in the OAuth API Script field. Remove it from the Confluence entry in the Application Registry.No scope records. Add the scope records to the OAuth entity profile.Callback URL typo. Correct the callback URL in the Atlassian app to https://<your-instance>.service-now.com/oauth_redirect.do.Missing scope. search:confluence is needed for activity, and write:confluence-groups for reclaim; add the scope in the Atlassian app and authorize again so the new token carries it.Setup by version. In 17.4.0 and earlier create the OAuth 2.0 (3LO) app in the Atlassian developer console, add the Confluence API permissions and copy the Client ID and secret; in 17.4.1 and later the app, Client ID, secret and redirect fields are not part of the dialog.Scope error on older Xanadu releases. Update SaaS License Management, then authorize again.Australia and later. The OAuth app must carry the scopes each flow needs; authorize again after adding them. Verify. A token is returned and validation succeeds. E. Token expired or the site ID cannot be retrievedSite ID cannot be retrieved. Check with your administrator{"error":"unauthorized_client","error_description":"refresh_token is invalid"}{"code":401,"message":"Unauthorized"}failed to get access token from remote oauth serverMissing parameters: access_token Symptoms. Site ID cannot be retrieved. Check with your administrator{"error":"unauthorized_client","error_description":"refresh_token is invalid"}Outbound: HTTP 401 {"code":401,"message":"Unauthorized"} on .../oauth/token/accessible-resources.Node log: failed to get access token from remote oauth server with Missing parameters: access_token.Profile banner: Last refresh failed ... check OAuth credentials and retry. Where to check. The OAuth 2.0 Credentials record for the connection; the Application Registry entry; the outbound log for the Atlassian auth host. Causes and fixes. Token expired. Open the OAuth 2.0 Credentials record and use Get OAuth Token for a new token, open the Application Registry entry and raise Refresh Token Lifespan, then rerun the failed jobs. The outbound request to the Atlassian auth host should now return 200.MFA on the authorizing account. If the Atlassian account has MFA that needs interactive approval, token refresh can fail after expiry. Relax MFA for the account used to authorize and authorize again, or accept re-authorizing manually.No access to the site. If the authorizing user cannot access the Confluence site, or the token was issued for another site, the site cannot be resolved. Authorize again with a site administrator who can access the site.Role for the lookup. The site lookup works only for users with sn_conflunce_spoke.confluence_cloud_admin; otherwise it silently returns nothing and the URL becomes /ex/confluence/undefined/wiki/.... Grant the role.Unauthorized (401) on other calls. Check the connection record on the alias and the roles and scopes granted when the token was issued.Atlassian changes. Atlassian can deprecate APIs or shorten token life; track expiry in the Atlassian console and update the spoke. Verify. The accessible-resources request returns 200 and the next run completes. F. Wrong site, Cloud ID or connection URL Symptoms. Requests go to a different Atlassian site; HTTP 404 on /wiki/...; the connection URL is rejected; validation fails with a host error. Where to check. The connection record's URL; the outbound request URL; the site list for the token. Causes and fixes. URL format. Use https://api.atlassian.com/ex/confluence/<Cloud-ID>. The host must be api.atlassian.com. The Cloud ID is taken from the Confluence product page in Atlassian Administration.URL without /ex/confluence. The integration then reads the token's accessible resources and uses the last site whose scopes include Confluence; with several sites granted to the token, the wrong site can be used. Put the Cloud ID in the connection URL.One site per profile. Create a profile and child alias per site (H).Atlassian API change (older spoke versions). Update the Confluence Cloud Spoke to the latest version. Verify. The outbound URL reads /ex/confluence/<Cloud-ID>/wiki/rest/api/... and returns 200. G. The job runs but no users are imported Symptoms. Job Completed with zero subscriptions and no error; the group picker shows nothing; only some groups' users appear. Where to check. Confluence Cloud > Confluence Groups (table sn_conflunce_spoke_confluence_groups) and its Add Groups related link; the user's roles. Causes and fixes. No groups selected. Only users in selected groups are retrieved and managed. Use Add Groups, choose the same Connection & Credential as the profile, and move the groups that grant Confluence access from Available to Selected. Select only groups that grant access; the Available list shows every group in the Atlassian account.Available list empty. The connection or the read:confluence-groups scope failed; fix authentication first (D, E).Picker shows nothing. The picker works only for users with sn_conflunce_spoke.confluence_cloud_admin.Wrong connection. Groups are stored per connection; selecting groups under another connection leaves this profile empty.Group retrieval failures (older versions). Update the Confluence Cloud Spoke. Verify. The flow execution shows each selected group with its members and subscriptions appear. H. Several Confluence sites, child aliases and alias errorsCannot override connection alias. Flow confluence_cloud_download_subscriptions already has an override configured for alias:<id>Error in getting connection details Symptoms. Only one Atlassian site can be tracked per profile.Cannot override connection alias. Flow confluence_cloud_download_subscriptions already has an override configured for alias:<id>A second profile shows the first site's users; New is missing on the Child Aliases tab.Error in getting connection details in the system log. Where to check. Flow Designer > the Confluence subflows > Configure Connections; the parent alias Confluence Cloud; the child aliases. Causes and fixes. Multiple sites. Not supported in one profile. Create one profile per site: on the parent alias set the Configuration template to match the ticked processes, open Child Aliases > New (switch to the Confluence Cloud Spoke application scope if New is missing), create a connection and credential on the child, select the child alias on the profile, save and publish.Override set on the subflow. Open Confluence Cloud Download Subscriptions and every nested subflow, open Configure Connections, reset the alias to Use Default Connection, and set the alias only on the integration profile.Child alias creation failed. The template lookup or alias creation failed; recreate the child from the parent alias.Groups per connection. Select the groups again for each child connection (G).Group membership with a different alias (older versions). Update the Confluence Cloud Spoke. Verify. Each profile imports only its own site's users and the scheduled job runs without the override error. 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 Atlassian error. The messages are summaries; open the flow execution and fix the step error (D, E, F, N, Q).Outdated application or spoke. Update SaaS License Management and the Confluence Cloud 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. Verify. The next run shows Completed and updated subscriptions. J. Too many or too few subscriptions(Deactivated or Unlicensed) Symptoms. Fewer users than Confluence shows; accounts with (Unlicensed), (Deactivated) or (Deactivated or Unlicensed) in the name appear as subscriptions; users disappear after a run. Where to check. The selected groups; the member requests for each group; exclusion rules; the subscriptions' display names. Causes and fixes. Group selection. Only members of the selected groups are counted (G).Unlicensed and deactivated accounts (older versions). Atlassian marks such accounts in the display name, and older versions imported them as subscriptions. Update to the 202402 line or later, then delete or exclude the old subscriptions created with those names.Users with the same display name (older versions). Update the application.One subscription type. All selected groups map to the single product Atlassian Confluence Cloud; groups that do not grant a license inflate the count, so select only access-granting groups.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. Verify. Counts match the licensed members of the selected groups. K. Identifier or software model problems Symptoms. A raw identifier and no software model; 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, CONFLUENCE_CLOUD, mapped to the Atlassian Confluence Cloud model.Unknown identifier. Open it under Unrecognized Subscription Identifiers, set the correct software model and save.Entitlements missing. Create entitlements for the generated models and run reconciliation. Verify. Every subscription shows the Atlassian Confluence Cloud model. L. Subscription user is empty or wrong Symptoms. Subscriptions with an Atlassian account but no User; records on the Subscriptions without user page; last activity not stamped for a matched user. Where to check. sys_user email and user ID versus the Atlassian email; User resolution rules; sn_itam_samp.user_resolution_exclude_table. Causes and fixes. Email missing or different. The group members request returns the email as Atlassian provides it; Atlassian privacy settings can leave it empty. Without an email the user cannot be matched. Align the data or add a user resolution rule (Software Asset Workspace > License operations > User subscription > User resolution rules), then rerun the refresh job.Empty email on the user. Last activity is not stamped when the matched user has no email; populate email on sys_user.Exact match needed. Older versions required an exact match; update the application.Same email in several user tables. List the extra tables in sn_itam_samp.user_resolution_exclude_table.Manual edits overwritten. The User field is recalculated each run. Verify. The subscription shows the intended user. M. Last activity is blank or stale Symptoms. Confluence subscriptions have no last activity, or it does not match what Confluence shows; users who only read content have none. Where to check. The activity job result; the content-search requests; the user's recent edits in Confluence. Causes and fixes. How activity works. The activity job searches content changed since the activity start date and credits the person who last updated each item (pages, blog posts, comments, attachments and spaces). Reading or viewing does not count. The exact set of events that counts is not further documented.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).Scope. search:confluence is required; without it the activity pull fails while the download succeeds (D).Date format. Use yyyy-MM-dd; ambiguous date values broke the last-activity comparison in older spoke versions (update to v1.2.6 or later).Look-back. Activity is read from the Analyze user activity from date (default 60 days), not from the profile creation date.Never cleared. Last activity only moves forward. Verify. A user who edited a page today shows today's date after the next activity run. N. Activity job errors{"statusCode":400,...,"message":"com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : "} Symptoms. {"statusCode":400,...,"message":"com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : "} during the activity run.The activity job fails while the subscription job succeeds. Where to check. The activity subflow execution; the outbound content-search request and its cql value. Causes and fixes. Date format. See C1.Scope missing. Add search:confluence and authorize again.Token problems. See E.Next-page links. Paging follows the next link of each result; very large result sets take long; keep the activity window reasonable.Older spoke. Update the Confluence Cloud Spoke. Verify. The activity job completes and last activity updates. O. No reclamation candidates for Confluence Symptoms. Inactive users get no removal candidate. Where to check. The Confluence 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.Workspace threshold list. The workspace rule form may offer fewer Last activity threshold choices than the classic form; set the value in the classic form.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).A reclamation flow that changes nothing. If a candidate is processed but the subscription is unchanged, check the reclaim steps (P). 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.Group ID is not provided.Account ID is not provided.No user exists for Account ID: <id>No group exists for Group ID: <id> Symptoms. The reclamation of user subscriptions will not be successful because the Reclaim subscription checkbox isn't selected on the integration profile.Group ID is not provided.Account ID is not provided.No user exists for Account ID: <id>No group exists for Group ID: <id>Invalid username or password, or failed connection. Check with your System Administrator.Unexpected error occurred. Check with your System Administrator.The user still has Confluence access after the candidate closed. Where to check. The candidate's banner; the Confluence Cloud Reclaim Subscription flow execution; the outbound DELETE request and its status; the Atlassian account's groups. Causes and fixes. What reclaim does. It looks up the user's group memberships and removes the user from the groups listed in the selected-groups table (HTTP 204 means success). It does not deactivate or change the Atlassian account. The license is freed only if the Confluence license is tied to that group.Reclaim not configured. Select Reclaim subscriptions, validate and publish.Not covered by validation. Validation does not test reclaim; test with one candidate.Permissions. Reclaim needs a site administrator and the write:confluence-groups scope. A 401 shows the Invalid username or password... message. For a 403 the integration should show an insufficient-permissions message, but it may fall through to Unexpected error occurred..., so check the outbound response for the real reason.Missing IDs. Account ID is not provided. or Group ID is not provided. means the subscription or group row lacks the Atlassian ID; rerun the download and recheck the selected groups.User or group already gone. No user exists... or No group exists...: the user or group was removed in Atlassian; rerun the download.Access remains. A user with access through another group that is not selected keeps access; add that group to the selection (G).Older spoke. A reclamation problem was fixed in spoke v1.2.4; update. Verify. The user is no longer in the selected groups, the candidate closes and the subscription is removed on the next run. Q. Limits, paging and timeouts Symptoms. Slow runs on large sites; HTTP 429 or 5xx in the outbound log; groups or members missing on large accounts. Where to check. The outbound log statuses and timing; page counts for the group, member and search requests. Causes and fixes. Paging. Groups are read 1,000 per page, group members and content search 200 per page, following the next link; large sites take longer.Throttling. The sources document no Atlassian rate-limit behavior for this integration. The REST steps have a retry policy enabled; if you see 429, avoid overlapping runs, rerun later and check the outbound log.Avoid overlap. Do not run the subscriptions and activity jobs at the same time.Flow reporting overhead. Keep com.snc.process_flow.reporting.level at OFF in production.Reachability. Make sure the instance can reach api.atlassian.com and the Atlassian auth host; if the integration runs through a MID Server, update the spoke for the latest MID security changes. Verify. A complete run without unhandled 429 or 5xx and a normal duration. R. Problems after a clone, upgrade or repair Symptoms. Validate or Publish missing after an upgrade; tokens fail after a clone; the profile form is missing fields; scopes errors after moving versions. 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.Validate missing after an upgrade. The upgrade fix script that enables Validate Connection runs as a scheduled job; check sys_trigger and let it finish.Credentials after a clone. Tokens are instance-specific; authorize again on the target instance, or disable the jobs there.Versions and scopes. Update SaaS License Management and the Confluence Cloud Spoke together; on 17.4.1 and later the OAuth app step is removed and the connection stops refreshing if it is not authorized again; on Australia and later re-check the scopes.Alias not honoured (older versions). Update the application and select the alias 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, spoke or profile typeServiceNow platform administratorInstall or update, validate, publishAtlassian token, scopes or consentAtlassian site administrator and integration ownerFix the app or scopes, get a new token, validateSite or Cloud IDSAM integration ownerCorrect the URL, authorize again, validateGroups not selectedSAM integration owner with an Atlassian administratorSelect the access-granting groups, run once, compare countsDate formatPlatform administratorSet yyyy-MM-dd, validate, update the applicationMapping or user resolutionSAM administratorMap identifiers or add rules, rerunActivitySAM integration ownerEnable activity, run after a good downloadReclaimSAM process owner and Atlassian site administratorReclaim one candidate first; confirm other access groupsClone, upgrade, repairPlatform ownerRestore out-of-box components, authorize again, validate, run once 7. Verification criteria and recovery evidence Verification layerEvidence requiredWhat does not satisfy itConfigurationPublished profile, valid token and scopes, correct Cloud ID, groups selectedA Published status after an unvalidated connection changeExecutionCompleted sam_saas_job_log row and a successful flow executionA scheduled job that existsCoverageSubscriptions match licensed members of the selected groupsTotal counts that include unlicensed or deactivated accountsMatchingModel and user on every subscriptionRaw identifiers as display namesActivityRecent last activity for a user who edited contentBlank activity read as inactivityReclaimOne reclaimed user removed from the selected groups in AtlassianCandidate closed without the Atlassian change 8. Escalation evidence to collect Versions of SaaS License Management, the Confluence Cloud Spoke and the platform; recent upgrades, repairs or clones.Profile status, selected options, alias or child alias, number of selected groups, and the date format property.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 Cloud ID 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 client secrets, tokens 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: Confluence Cloud Download Subscriptions (child Confluence Cloud Look up Group Members), Confluence Cloud Update User Activity, Confluence Cloud Reclaim Subscription.Spoke: parent alias Confluence Cloud and child aliases; group table sn_conflunce_spoke_confluence_groups; role sn_conflunce_spoke.confluence_cloud_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 glide.sys.date_format — keep yyyy-MM-dd for validation and activity.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, CONFLUENCE_CLOUD.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 content updates found by search; reading does not count; the look-back default is 60 days.Reclaim removes the user from the selected groups; the Atlassian account stays active.Validation covers download and activity, not reclaim. Known limitations One Atlassian site per profile; Confluence Cloud only.Which content events count as activity is not documented beyond the five event types recorded.Atlassian rate limits are not documented for this integration. Documentation ServiceNow product documentation for your release: Integrate with Confluence Cloud under Software Asset Management > SaaS License Management.Atlassian developer documentation: OAuth 2.0 (3LO), Confluence Cloud REST API scopes and CQL.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 Confluence Cloud 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 Atlassian 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 Confluence Cloud 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 Confluence Cloud 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 Atlassian 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.