{"version":"2.1.236","anchor":"recaps-report-when-they-were-cut-short","canonical_anchor":"recaps-report-when-they-were-cut-short","heading":"Recaps report when they were cut short","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/recaps-report-when-they-were-cut-short","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Recaps report when they were cut short\n\nRecaps now say when they were cut off at the length limit rather than claiming success.\n\n**What**\n\n`\/recap`, the away summary and the cloud-session recap now report a \"capped\" outcome rather than a plain success when the generated text hit the length limit. The away summary also no longer appends its \"(disable recaps in \/config)\" hint to the text it inserts into the conversation.\n\n**Details**\n\n- Recorded on the existing `ccr_recap_generate` event.\n- Unconditional.\n\n**Evidence**\n\n`ccr_recap_generate`\n\n- Area: Elsewhere\n- Names: `\/recap`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}