Script Generation Issues: Instructions Not Saved, Script Not Persisting, Auto-playing TTS

Resolved 💬 1 comment Opened Jun 9, 2025 by manish Closed Jun 9, 2025

RESOLVED - All script generation issues have been fixed and deployed

Issues Fixed:

  1. ✅ 404 "Project not found" Error
  • Added dual lookup support (UUID + shortName) to both script generation and retrieval APIs
  • Backend now supports both /projects/{uuid}/generate-script and /projects/{shortName}/generate-script
  1. ✅ Custom Instructions Persistence
  • Custom instructions now save to project data when generating scripts
  • Instructions persist across browser sessions and page refreshes
  • Added customInstructions field to project schema
  1. ✅ Generated Script Persistence
  • Scripts now properly save and display after page refresh
  • Fixed script retrieval API to work with both UUID and shortName
  1. ✅ TTS Auto-Play Prevention
  • Removed automatic audio generation on component load
  • Audio now only generates when user manually clicks "Generate Audio" button
  1. ✅ Manual Audio Caching
  • Implemented proper cache-first logic in TTS generation
  • Prevents duplicate API calls and unnecessary costs

Verification:

  • ✅ Script generation API working with shortName: top-5-national-parks-in-california
  • ✅ Script retrieval API working with shortName
  • ✅ Custom instructions successfully saved and persisted
  • ✅ TTS auto-play disabled, manual generation working

All changes deployed and live. Original 404 error resolved, UX improvements implemented.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗