{"version":"2.1.238","anchor":"transcript-upload-timeouts-no-longer-blamed-on-payload-size","canonical_anchor":"transcript-upload-timeouts-no-longer-blamed-on-payload-size","heading":"Transcript upload timeouts no longer blamed on payload size","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/transcript-upload-timeouts-no-longer-blamed-on-payload-size","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Transcript upload timeouts no longer blamed on payload size\n\nA slow transcript upload now says it timed out instead of wrongly blaming the file size.\n\n**What**\n\nSharing a transcript that timed out on a large upload was reported as the payload being too large. Only a real HTTP 413 or a payload range error counts as too large now, so a slow upload reports as a timeout.\n\n**Details**\n\n- The hardcoded 30000 ms upload timeout was moved into a named constant; the value is unchanged.\n\n**Evidence**\n\n`payloadTooLarge: r === \"http_413\" || r === \"payload_range_error\",`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}