conversation.dropped

Schema

This event is emitted when a request will get no reply. Either a guardrail stopped the conversation with its answer option set to false, or the request's maxProcessingTimeSeconds limit, where it applies, ran out before a reply came: the request waited too long, or it could not be answered because the conversation was already stopped, a profile could not be found, or the generation failed. The payload does not say which. Your project logs record a request refused on a stopped conversation (content_creation.chat_model.refusal) and a missing profile (content_creation.conversation.profile_not_found).