{"version":"2.1.321","anchor":"connector-upload-target-expiresat-parsing-simplified","canonical_anchor":"connector-upload-target-expiresat-parsing-simplified","heading":"Connector uploads no longer fail on a bad expiry date","tier":"notice","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/connector-upload-target-expiresat-parsing-simplified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Connector uploads no longer fail on a bad expiry date\n\nAn upload target with an invalid `expiresAt` date is now treated as having no expiry, instead of being rejected\n\n**What**\n\nConnectors link Claude Code to outside services. When a connector gives an upload destination whose `expiresAt` date is not valid, Claude Code now logs this and treats it as having no expiry. Before, it rejected the destination as malformed.\n\n**Why**\n\nUploads through connectors keep working when the service sends a badly formatted expiry date.\n\n- Area: Connectors\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}