record_lifecycle_renewals
Retain due renewal-window events for one project without sending messages or changing monitoring state. Repeated calls do not duplicate a window.
Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
This operation changes saved state. Review its inputs and retry behavior before calling.
Example request
Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.Returned result
Schema-validated example; IDs and dates are illustrative. MCP returns this data instructuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.
Input fields
Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.Validation and omitted values
Retain due renewal-window events for the selected project. This operation does not change deal fields, send messages or change monitoring state; repeating it does not duplicate an existing window. Use update_link_lifecycle to change costs, dates or contact metadata at the observed revision. Costs use integer currency minor units; set or clear costMinor and currency together. Omitted update fields remain unchanged; explicit null clears a field.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
Download input schema · Download output schema