teams-meeting-pipeline

Use the hermes teams-pipeline CLI to list recent meeting jobs, then replay a specific job with its ID to regenerate the summary and action items. The pipeline is subscription-driven, so new meetings are ingested automatically via Graph webhooks.

Missing summaries are usually caused by expired Microsoft Graph webhook subscriptions, which cap at 72 hours without auto-renewal. Run the subscriptions command to check expiration, then recreate the subscription and schedule automated renewal every 12 hours.

The pipeline requires an Azure AD app registration with admin-consented Graph application permissions, plus tenant ID, client ID, and client secret environment variables. A token can acquire cleanly while API calls still return 401 or 403 if admin consent was not re-granted after adding permissions.

List jobs filtered by failed status to find the job ID, then run the replay command with that ID to re-summarize and re-deliver. If it fails again, inspect the job detail and dry-run transcript resolution with the fetch command.

Teams takes time to generate the transcript artifact after a meeting ends, so an immediate fetch may return empty. Wait two to five minutes and retry, or let the Graph webhook drive ingestion naturally.