---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/b50bf0c50190206c6dc6e16a0debf379/screenshot/b6803363-e2e0-4e7f-a907-cc1a71be088f.png"
url: "https://jam.dev/c/8ed8dc9c-0c83-4021-94e8-adc3e9662e15"
capturedOn: "https://home.aisquare.studio/studio-manager?tab=experiences"
type: "video"
browser: "Chrome 138.0.7204.101"
os: "macOS (arm) 15.5.0"
screen: "1124x812"
country: "IN"
timezone: "Asia/Calcutta"
author: "Surjoyday Talukdar"
date: "2025-07-16T11:40:56.285Z"
---

Publishing AI experience fails after changing studio name
Steps:
Go to Studio Manager > AI Experiences.
Click 'Edit' on a draft AI Experience (00:01).
Navigate to the 'Categorize & Publish' step.
Click 'Use Default Studio' (00:07).
Click the edit icon next to 'Studio Name' (00:10).
Modify the 'Studio Name' (00:14).
Click 'Next: Review' (00:15).
Click 'Publish to AI Studio' (00:19).
Observe the 'Failed to publish. Please try again.' error.

## Comments

**Surjoyday Talukdar** · 2025-07-16T11:40:56.285Z

Publishing AI experience fails after changing studio name
__Steps:__
1. Go to Studio Manager > AI Experiences.
2. Click 'Edit' on a draft AI Experience (00:01).
3. Navigate to the 'Categorize & Publish' step.
4. Click 'Use Default Studio' (00:07).
5. Click the edit icon next to 'Studio Name' (00:10).
6. Modify the 'Studio Name' (00:14).
7. Click 'Next: Review' (00:15).
8. Click 'Publish to AI Studio' (00:19).
9. Observe the 'Failed to publish. Please try again.' error.

## Not in this document

This is the summary tier. The captured events — console logs, network requests, user actions, and video frames — are not here: reading them needs filters, paging, and auth, so they live behind the Jam MCP server and CLI. Start at `getDetails`.

MCP: `https://mcp.jam.dev/mcp` (setup: https://jam.dev/docs/jam-mcp). CLI: `curl -fsSL https://native.jam.dev/install | bash` (https://jam.dev/docs/cli).