Is there an existing issue for this?

• I have searched the existing issues

What happened?

Issue Overview
The fetch-transcript function silently fails when errors occur during Supabase database updates. This leads to data inconsistency, where transcripts may not be saved without any error reporting or user notification.

Steps to Reproduce

1. Deploy the fetch-transcript function with valid Supabase credentials
2. Trigger the function with a valid meeting_url and meeting_id
3. Simulate a database error by:
   • Using an invalid meeting_id, OR
   • Temporarily removing table permissions, OR
   • Introducing a schema mismatch
4. Observe that the function completes with a successful response despite the failed database update

Expected Behaviour

• The function should validate database update results
• Any update failures should throw exceptions and be properly logged
• transcription_attempted_at should only update when the transaction succeeds
• Users should receive clear error messages for database failures

Actual Behaviour

• Database updates fail silently without error propagation
• Transcripts are lost without any notification
• Function returns success even when data isn't persisted
• No error logging for database operation failures

Suggested Improvements
Add proper error handling for Supabase update operations

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue