BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Workflow Exit//Shutdown tracker//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
NAME:Platform shutdowns (Workflow Exit)
X-WR-CALNAME:Platform shutdowns (Workflow Exit)
DESCRIPTION:Shutdown dates of automation\, AI and developer platforms\, che
 cked against the vendors' own announcements. https://workflowexit.com/shut
 downs
X-WR-CALDESC:Shutdown dates of automation\, AI and developer platforms\, ch
 ecked against the vendors' own announcements. https://workflowexit.com/shu
 tdowns
REFRESH-INTERVAL;VALUE=DURATION:P1D
X-PUBLISHED-TTL:P1D
BEGIN:VEVENT
UID:openai-legacy-models-first-batch-stops-working@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261023
DTEND;VALUE=DATE:20261024
SUMMARY:OpenAI older models: first batch stops working
DESCRIPTION:OpenAI API: older models and snapshots (GPT-3.5 Turbo\, GPT-4\,
  GPT-4 Turbo\, o1\, o3-mini\, o4-mini\, gpt-image-1\, GPT-5 2025 snapshots
 \, GPT-5.1)\nVendor: OpenAI\nOctober 23\, 2026: first batch stops working 
 (gpt-3.5-turbo\, gpt-4\, gpt-4-turbo\, gpt-4-1106-preview\, gpt-4.1-nano\,
  gpt-4o-2024-05-13\, o1\, o1-pro\, o3-mini\, o4-mini\, gpt-image-1\, and f
 ine-tunes of gpt-3.5-turbo\, gpt-4\, gpt-4.1-nano\, babbage-002 and davinc
 i-002)\nWhat stops: API calls to these model IDs fail after their shutdown
  dates\, and the listed fine-tuned models are removed on 2026-10-23.\nData
  deleted: Not announced. No account data deletion is announced for base mo
 dels. The listed fine-tuned versions are removed on 2026-10-23\; the notic
 e does not say what happens to their training files\nWhere to move: Offici
 al: switch to the substitutes OpenAI lists per model (gpt-5.6-sol\, gpt-5.
 6-terra or gpt-5.6-luna for text\; gpt-image-2.5-sunburst or gpt-image-2.5
 -flare for images\; gpt-6-sol or gpt-6-luna for gpt-5.1\, gpt-5.3-codex\, 
 gpt-5.4-nano)\; Re-test prompts\, structured output and tool calls after s
 witching\; pin dated snapshots\; Or point the same automation step at anot
 her provider (Anthropic\, Google Gemini)\nDetails and sources: https://wor
 kflowexit.com/shutdowns#openai-legacy-models
URL:https://workflowexit.com/shutdowns#openai-legacy-models
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-legacy-models-image-models-stop-working@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:OpenAI older models: image models stop working
DESCRIPTION:OpenAI API: older models and snapshots (GPT-3.5 Turbo\, GPT-4\,
  GPT-4 Turbo\, o1\, o3-mini\, o4-mini\, gpt-image-1\, GPT-5 2025 snapshots
 \, GPT-5.1)\nVendor: OpenAI\nDecember 1\, 2026: image models stop working 
 (gpt-image-1-mini\, gpt-image-1.5\, chatgpt-image-latest)\nWhat stops: API
  calls to these model IDs fail after their shutdown dates\, and the listed
  fine-tuned models are removed on 2026-10-23.\nData deleted: Not announced
 . No account data deletion is announced for base models. The listed fine-t
 uned versions are removed on 2026-10-23\; the notice does not say what hap
 pens to their training files\nWhere to move: Official: switch to the subst
 itutes OpenAI lists per model (gpt-5.6-sol\, gpt-5.6-terra or gpt-5.6-luna
  for text\; gpt-image-2.5-sunburst or gpt-image-2.5-flare for images\; gpt
 -6-sol or gpt-6-luna for gpt-5.1\, gpt-5.3-codex\, gpt-5.4-nano)\; Re-test
  prompts\, structured output and tool calls after switching\; pin dated sn
 apshots\; Or point the same automation step at another provider (Anthropic
 \, Google Gemini)\nDetails and sources: https://workflowexit.com/shutdowns
 #openai-legacy-models
URL:https://workflowexit.com/shutdowns#openai-legacy-models
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-legacy-models-gpt-5-and-o3-2025-snapshots-stop-working@workflowe
 xit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261211
DTEND;VALUE=DATE:20261212
SUMMARY:OpenAI older models: GPT-5 and o3 2025 snapshots stop working
DESCRIPTION:OpenAI API: older models and snapshots (GPT-3.5 Turbo\, GPT-4\,
  GPT-4 Turbo\, o1\, o3-mini\, o4-mini\, gpt-image-1\, GPT-5 2025 snapshots
 \, GPT-5.1)\nVendor: OpenAI\nDecember 11\, 2026: GPT-5 and o3 2025 snapsho
 ts stop working (gpt-5-2025-08-07\, gpt-5-mini-2025-08-07\, gpt-5-nano-202
 5-08-07\, gpt-5-pro-2025-10-06\, o3-2025-04-16\, o3-pro-2025-06-10)\nWhat 
 stops: API calls to these model IDs fail after their shutdown dates\, and 
 the listed fine-tuned models are removed on 2026-10-23.\nData deleted: Not
  announced. No account data deletion is announced for base models. The lis
 ted fine-tuned versions are removed on 2026-10-23\; the notice does not sa
 y what happens to their training files\nWhere to move: Official: switch to
  the substitutes OpenAI lists per model (gpt-5.6-sol\, gpt-5.6-terra or gp
 t-5.6-luna for text\; gpt-image-2.5-sunburst or gpt-image-2.5-flare for im
 ages\; gpt-6-sol or gpt-6-luna for gpt-5.1\, gpt-5.3-codex\, gpt-5.4-nano)
 \; Re-test prompts\, structured output and tool calls after switching\; pi
 n dated snapshots\; Or point the same automation step at another provider 
 (Anthropic\, Google Gemini)\nDetails and sources: https://workflowexit.com
 /shutdowns#openai-legacy-models
URL:https://workflowexit.com/shutdowns#openai-legacy-models
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-legacy-models-gpt-5-1-and-others-stop-working@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270401
DTEND;VALUE=DATE:20270402
SUMMARY:OpenAI older models: GPT-5.1 and others stop working
DESCRIPTION:OpenAI API: older models and snapshots (GPT-3.5 Turbo\, GPT-4\,
  GPT-4 Turbo\, o1\, o3-mini\, o4-mini\, gpt-image-1\, GPT-5 2025 snapshots
 \, GPT-5.1)\nVendor: OpenAI\nApril 1\, 2027: GPT-5.1 and others stop worki
 ng (gpt-5.1\, gpt-5.3-codex\, gpt-5.4-nano)\nWhat stops: API calls to thes
 e model IDs fail after their shutdown dates\, and the listed fine-tuned mo
 dels are removed on 2026-10-23.\nData deleted: Not announced. No account d
 ata deletion is announced for base models. The listed fine-tuned versions 
 are removed on 2026-10-23\; the notice does not say what happens to their 
 training files\nWhere to move: Official: switch to the substitutes OpenAI 
 lists per model (gpt-5.6-sol\, gpt-5.6-terra or gpt-5.6-luna for text\; gp
 t-image-2.5-sunburst or gpt-image-2.5-flare for images\; gpt-6-sol or gpt-
 6-luna for gpt-5.1\, gpt-5.3-codex\, gpt-5.4-nano)\; Re-test prompts\, str
 uctured output and tool calls after switching\; pin dated snapshots\; Or p
 oint the same automation step at another provider (Anthropic\, Google Gemi
 ni)\nDetails and sources: https://workflowexit.com/shutdowns#openai-legacy
 -models
URL:https://workflowexit.com/shutdowns#openai-legacy-models
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:hubspot-legacy-apis-no-new-legacy-private-apps@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261026
DTEND;VALUE=DATE:20261027
SUMMARY:HubSpot legacy APIs and apps: no new legacy private apps
DESCRIPTION:HubSpot legacy APIs (v1-v3\, v4\, v1 OAuth\, Pipelines v1) and 
 legacy public/private apps\nVendor: HubSpot\nOctober 26\, 2026: no new leg
 acy private apps (for existing accounts\; new accounts lost the option on 
 2026-09-28)\nWhat stops: Pipelines v1 and v1 OAuth calls stop working on t
 heir sunset dates\, new legacy private apps cannot be created\, and all /v
 1-/v3 endpoints plus legacy apps lose support in September 2027.\nData del
 eted: No. No CRM data is deleted\; integrations break or lose support\nWhe
 re to move: Official: migrate straight to date-based versioned (DBV) APIs\
 , e.g. Pipelines API 2026-09 and OAuth /oauth/2026-03/token\, /introspect\
 , /revoke\; Official: Service Keys for new private integrations\; Projects
 -based model for public and private apps\; Update HubSpot steps in Zapier\
 , Make\, n8n or custom code once the connector supports the new versions\n
 Details and sources: https://workflowexit.com/shutdowns#hubspot-legacy-api
 s
URL:https://workflowexit.com/shutdowns#hubspot-legacy-apis
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:hubspot-legacy-apis-pipelines-api-v1-stops-working@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261204
DTEND;VALUE=DATE:20261205
SUMMARY:HubSpot legacy APIs and apps: Pipelines API v1 stops working
DESCRIPTION:HubSpot legacy APIs (v1-v3\, v4\, v1 OAuth\, Pipelines v1) and 
 legacy public/private apps\nVendor: HubSpot\nDecember 4\, 2026: Pipelines 
 API v1 stops working\nWhat stops: Pipelines v1 and v1 OAuth calls stop wor
 king on their sunset dates\, new legacy private apps cannot be created\, a
 nd all /v1-/v3 endpoints plus legacy apps lose support in September 2027.\
 nData deleted: No. No CRM data is deleted\; integrations break or lose sup
 port\nWhere to move: Official: migrate straight to date-based versioned (D
 BV) APIs\, e.g. Pipelines API 2026-09 and OAuth /oauth/2026-03/token\, /in
 trospect\, /revoke\; Official: Service Keys for new private integrations\;
  Projects-based model for public and private apps\; Update HubSpot steps i
 n Zapier\, Make\, n8n or custom code once the connector supports the new v
 ersions\nDetails and sources: https://workflowexit.com/shutdowns#hubspot-l
 egacy-apis
URL:https://workflowexit.com/shutdowns#hubspot-legacy-apis
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:hubspot-legacy-apis-v1-oauth-api-stops-working@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270216
DTEND;VALUE=DATE:20270217
SUMMARY:HubSpot legacy APIs and apps: v1 OAuth API stops working
DESCRIPTION:HubSpot legacy APIs (v1-v3\, v4\, v1 OAuth\, Pipelines v1) and 
 legacy public/private apps\nVendor: HubSpot\nFebruary 16\, 2027: v1 OAuth 
 API stops working (POST /v1/token and the access and refresh token lookup 
 and delete endpoints)\nWhat stops: Pipelines v1 and v1 OAuth calls stop wo
 rking on their sunset dates\, new legacy private apps cannot be created\, 
 and all /v1-/v3 endpoints plus legacy apps lose support in September 2027.
 \nData deleted: No. No CRM data is deleted\; integrations break or lose su
 pport\nWhere to move: Official: migrate straight to date-based versioned (
 DBV) APIs\, e.g. Pipelines API 2026-09 and OAuth /oauth/2026-03/token\, /i
 ntrospect\, /revoke\; Official: Service Keys for new private integrations\
 ; Projects-based model for public and private apps\; Update HubSpot steps 
 in Zapier\, Make\, n8n or custom code once the connector supports the new 
 versions\nDetails and sources: https://workflowexit.com/shutdowns#hubspot-
 legacy-apis
URL:https://workflowexit.com/shutdowns#hubspot-legacy-apis
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:hubspot-legacy-apis-v4-apis-lose-support@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270330
DTEND;VALUE=DATE:20270331
SUMMARY:HubSpot legacy APIs and apps: v4 APIs lose support
DESCRIPTION:HubSpot legacy APIs (v1-v3\, v4\, v1 OAuth\, Pipelines v1) and 
 legacy public/private apps\nVendor: HubSpot\nMarch 30\, 2027: v4 APIs lose
  support\nWhat stops: Pipelines v1 and v1 OAuth calls stop working on thei
 r sunset dates\, new legacy private apps cannot be created\, and all /v1-/
 v3 endpoints plus legacy apps lose support in September 2027.\nData delete
 d: No. No CRM data is deleted\; integrations break or lose support\nWhere 
 to move: Official: migrate straight to date-based versioned (DBV) APIs\, e
 .g. Pipelines API 2026-09 and OAuth /oauth/2026-03/token\, /introspect\, /
 revoke\; Official: Service Keys for new private integrations\; Projects-ba
 sed model for public and private apps\; Update HubSpot steps in Zapier\, M
 ake\, n8n or custom code once the connector supports the new versions\nDet
 ails and sources: https://workflowexit.com/shutdowns#hubspot-legacy-apis
URL:https://workflowexit.com/shutdowns#hubspot-legacy-apis
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:hubspot-legacy-apis-v1-v3-apis-and-legacy-apps-lose-support@workflowexi
 t.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270901
DTEND;VALUE=DATE:20270902
SUMMARY:HubSpot legacy APIs and apps: v1-v3 APIs and legacy apps lose suppo
 rt (September 2027\, exact day not announced)
DESCRIPTION:HubSpot legacy APIs (v1-v3\, v4\, v1 OAuth\, Pipelines v1) and 
 legacy public/private apps\nVendor: HubSpot\nSeptember 2027: v1-v3 APIs an
 d legacy apps lose support\nWhat stops: Pipelines v1 and v1 OAuth calls st
 op working on their sunset dates\, new legacy private apps cannot be creat
 ed\, and all /v1-/v3 endpoints plus legacy apps lose support in September 
 2027.\nData deleted: No. No CRM data is deleted\; integrations break or lo
 se support\nWhere to move: Official: migrate straight to date-based versio
 ned (DBV) APIs\, e.g. Pipelines API 2026-09 and OAuth /oauth/2026-03/token
 \, /introspect\, /revoke\; Official: Service Keys for new private integrat
 ions\; Projects-based model for public and private apps\; Update HubSpot s
 teps in Zapier\, Make\, n8n or custom code once the connector supports the
  new versions\nDetails and sources: https://workflowexit.com/shutdowns#hub
 spot-legacy-apis
URL:https://workflowexit.com/shutdowns#hubspot-legacy-apis
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:amazon-pinpoint-closed-to-new-customers@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20250520
DTEND;VALUE=DATE:20250521
SUMMARY:Amazon Pinpoint: closed to new customers
DESCRIPTION:Amazon Pinpoint engagement features (endpoints\, segments\, cam
 paigns\, journeys\, analytics)\nVendor: Amazon Web Services\nMay 20\, 2025
 : closed to new customers\nWhat stops: The Pinpoint console\, endpoints\, 
 segments\, campaigns\, journeys\, in-app messaging\, recommenders and anal
 ytics/KPI APIs go away\; push\, OTP and phone-number validation continue\,
  and SMS/voice/email sending continues for existing customers.\nData delet
 ed: Not announced. AWS says resources become inaccessible and tells custom
 ers to export endpoints (segment export)\, segments\, campaigns and journe
 ys (get-* APIs)\, templates and up to 3 months of KPIs first\; no deletion
  date is stated\nWhere to move: Official: Amazon Connect outbound campaign
 s and Customer Profiles for engagement\; Official: AWS End User Messaging 
 (SMS\, voice\, push)\, Amazon SES (email)\, Amazon Kinesis (events)\; Enga
 gement SaaS (Braze\, Customer.io\, OneSignal) or simple journeys rebuilt i
 n n8n calling SES / End User Messaging\nDetails and sources: https://workf
 lowexit.com/shutdowns#amazon-pinpoint
URL:https://workflowexit.com/shutdowns#amazon-pinpoint
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:amazon-pinpoint-engagement-features-end@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261030
DTEND;VALUE=DATE:20261031
SUMMARY:Amazon Pinpoint: engagement features end
DESCRIPTION:Amazon Pinpoint engagement features (endpoints\, segments\, cam
 paigns\, journeys\, analytics)\nVendor: Amazon Web Services\nOctober 30\, 
 2026: engagement features end (console\, endpoints\, segments\, campaigns 
 and journeys no longer accessible)\nWhat stops: The Pinpoint console\, end
 points\, segments\, campaigns\, journeys\, in-app messaging\, recommenders
  and analytics/KPI APIs go away\; push\, OTP and phone-number validation c
 ontinue\, and SMS/voice/email sending continues for existing customers.\nD
 ata deleted: Not announced. AWS says resources become inaccessible and tel
 ls customers to export endpoints (segment export)\, segments\, campaigns a
 nd journeys (get-* APIs)\, templates and up to 3 months of KPIs first\; no
  deletion date is stated\nWhere to move: Official: Amazon Connect outbound
  campaigns and Customer Profiles for engagement\; Official: AWS End User M
 essaging (SMS\, voice\, push)\, Amazon SES (email)\, Amazon Kinesis (event
 s)\; Engagement SaaS (Braze\, Customer.io\, OneSignal) or simple journeys 
 rebuilt in n8n calling SES / End User Messaging\nDetails and sources: http
 s://workflowexit.com/shutdowns#amazon-pinpoint
URL:https://workflowexit.com/shutdowns#amazon-pinpoint
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-agent-builder-existing-evals-become-read-only@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261031
DTEND;VALUE=DATE:20261101
SUMMARY:OpenAI Agent Builder: existing evals become read-only
DESCRIPTION:OpenAI Agent Builder\, Evals and reusable prompts\nVendor: Open
 AI\nOctober 31\, 2026: existing evals become read-only\nWhat stops: The vi
 sual Agent Builder\, hosted workflow IDs run through ChatKit\, the Evals p
 latform and the v1/prompts API. ChatKit\, the Agents SDK and the Responses
  API stay.\nData deleted: Not announced. OpenAI publishes no export or del
 etion details for workflow definitions\, prompts or eval results\, so copy
  them before the dates\nWhere to move: Official: Agents SDK (code export) 
 or ChatGPT Workspace Agents\; Official: Promptfoo for Evals\; inline the p
 rompt text for reusable prompts\; n8n (AI Agent node)\, Langflow or Dify\n
 Migration guide: https://workflowexit.com/openai-agent-builder-to-n8n\nDet
 ails and sources: https://workflowexit.com/shutdowns#openai-agent-builder
URL:https://workflowexit.com/shutdowns#openai-agent-builder
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-agent-builder-agent-builder-evals-and-v1-prompts-shut-down@workf
 lowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261130
DTEND;VALUE=DATE:20261201
SUMMARY:OpenAI Agent Builder: Agent Builder\, Evals and v1/prompts shut dow
 n
DESCRIPTION:OpenAI Agent Builder\, Evals and reusable prompts\nVendor: Open
 AI\nNovember 30\, 2026: Agent Builder\, Evals and v1/prompts shut down\nWh
 at stops: The visual Agent Builder\, hosted workflow IDs run through ChatK
 it\, the Evals platform and the v1/prompts API. ChatKit\, the Agents SDK a
 nd the Responses API stay.\nData deleted: Not announced. OpenAI publishes 
 no export or deletion details for workflow definitions\, prompts or eval r
 esults\, so copy them before the dates\nWhere to move: Official: Agents SD
 K (code export) or ChatGPT Workspace Agents\; Official: Promptfoo for Eval
 s\; inline the prompt text for reusable prompts\; n8n (AI Agent node)\, La
 ngflow or Dify\nMigration guide: https://workflowexit.com/openai-agent-bui
 lder-to-n8n\nDetails and sources: https://workflowexit.com/shutdowns#opena
 i-agent-builder
URL:https://workflowexit.com/shutdowns#openai-agent-builder
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:oracle-apiary-shut-down-instances-deleted@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261031
DTEND;VALUE=DATE:20261101
SUMMARY:Oracle Apiary: shut down\, instances deleted
DESCRIPTION:Oracle Apiary (apiary.io) Cloud Service\nVendor: Oracle\nOctobe
 r 31\, 2026: shut down\, instances deleted\nWhat stops: Apiary Standard an
 d Professional (API Blueprint design\, docs and mocks) can no longer be us
 ed.\nData deleted: Yes. Oracle: all remaining instances will be permanentl
 y deleted after the EOL date\nWhere to move: Official: convert API Bluepri
 nt to OpenAPI\, then move to Apimatic\, Postman\, Swagger Editor\, Stoplig
 ht\, Redocly or Bump.sh\nDetails and sources: https://workflowexit.com/shu
 tdowns#oracle-apiary
URL:https://workflowexit.com/shutdowns#oracle-apiary
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:aws-lambda-runtimes-python3-10-deprecated@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261031
DTEND;VALUE=DATE:20261101
SUMMARY:AWS Lambda old runtimes: python3.10 deprecated
DESCRIPTION:AWS Lambda deprecated managed runtimes (Node.js 16/18/20/22\, P
 ython 3.8/3.9/3.10\, Ruby 3.2/3.3\, .NET 6/8\, Java 8\, Go 1.x\, provided\
 , provided.al2)\nVendor: Amazon Web Services\nOctober 31\, 2026: python3.1
 0 deprecated (no more security patches or support)\nWhat stops: From 2027-
 07-29 new functions cannot use deprecated runtimes and from 2027-08-31 the
 ir code and configuration cannot be updated\; existing functions can still
  be invoked.\nData deleted: No. Functions are not deleted\; deprecated run
 times get no security patches\nWhere to move: Official: upgrade to a suppo
 rted runtime (nodejs24.x\, python3.12-3.14\, java21/java25\, dotnet10\, pr
 ovided.al2023)\; Move small glue or cron functions that are not worth upgr
 ading to a workflow tool or another FaaS\nDetails and sources: https://wor
 kflowexit.com/shutdowns#aws-lambda-runtimes
URL:https://workflowexit.com/shutdowns#aws-lambda-runtimes
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:aws-lambda-runtimes-dotnet8-deprecated@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261110
DTEND;VALUE=DATE:20261111
SUMMARY:AWS Lambda old runtimes: dotnet8 deprecated
DESCRIPTION:AWS Lambda deprecated managed runtimes (Node.js 16/18/20/22\, P
 ython 3.8/3.9/3.10\, Ruby 3.2/3.3\, .NET 6/8\, Java 8\, Go 1.x\, provided\
 , provided.al2)\nVendor: Amazon Web Services\nNovember 10\, 2026: dotnet8 
 deprecated\nWhat stops: From 2027-07-29 new functions cannot use deprecate
 d runtimes and from 2027-08-31 their code and configuration cannot be upda
 ted\; existing functions can still be invoked.\nData deleted: No. Function
 s are not deleted\; deprecated runtimes get no security patches\nWhere to 
 move: Official: upgrade to a supported runtime (nodejs24.x\, python3.12-3.
 14\, java21/java25\, dotnet10\, provided.al2023)\; Move small glue or cron
  functions that are not worth upgrading to a workflow tool or another FaaS
 \nDetails and sources: https://workflowexit.com/shutdowns#aws-lambda-runti
 mes
URL:https://workflowexit.com/shutdowns#aws-lambda-runtimes
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:aws-lambda-runtimes-nodejs22-x-deprecated@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270430
DTEND;VALUE=DATE:20270501
SUMMARY:AWS Lambda old runtimes: nodejs22.x deprecated
DESCRIPTION:AWS Lambda deprecated managed runtimes (Node.js 16/18/20/22\, P
 ython 3.8/3.9/3.10\, Ruby 3.2/3.3\, .NET 6/8\, Java 8\, Go 1.x\, provided\
 , provided.al2)\nVendor: Amazon Web Services\nApril 30\, 2027: nodejs22.x 
 deprecated\nWhat stops: From 2027-07-29 new functions cannot use deprecate
 d runtimes and from 2027-08-31 their code and configuration cannot be upda
 ted\; existing functions can still be invoked.\nData deleted: No. Function
 s are not deleted\; deprecated runtimes get no security patches\nWhere to 
 move: Official: upgrade to a supported runtime (nodejs24.x\, python3.12-3.
 14\, java21/java25\, dotnet10\, provided.al2023)\; Move small glue or cron
  functions that are not worth upgrading to a workflow tool or another FaaS
 \nDetails and sources: https://workflowexit.com/shutdowns#aws-lambda-runti
 mes
URL:https://workflowexit.com/shutdowns#aws-lambda-runtimes
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:aws-lambda-runtimes-no-new-functions-on-deprecated-runtimes@workflowexi
 t.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270729
DTEND;VALUE=DATE:20270730
SUMMARY:AWS Lambda old runtimes: no new functions on deprecated runtimes
DESCRIPTION:AWS Lambda deprecated managed runtimes (Node.js 16/18/20/22\, P
 ython 3.8/3.9/3.10\, Ruby 3.2/3.3\, .NET 6/8\, Java 8\, Go 1.x\, provided\
 , provided.al2)\nVendor: Amazon Web Services\nJuly 29\, 2027: no new funct
 ions on deprecated runtimes\nWhat stops: From 2027-07-29 new functions can
 not use deprecated runtimes and from 2027-08-31 their code and configurati
 on cannot be updated\; existing functions can still be invoked.\nData dele
 ted: No. Functions are not deleted\; deprecated runtimes get no security p
 atches\nWhere to move: Official: upgrade to a supported runtime (nodejs24.
 x\, python3.12-3.14\, java21/java25\, dotnet10\, provided.al2023)\; Move s
 mall glue or cron functions that are not worth upgrading to a workflow too
 l or another FaaS\nDetails and sources: https://workflowexit.com/shutdowns
 #aws-lambda-runtimes
URL:https://workflowexit.com/shutdowns#aws-lambda-runtimes
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:aws-lambda-runtimes-no-updates-to-functions-on-deprecated-runtimes@work
 flowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270831
DTEND;VALUE=DATE:20270901
SUMMARY:AWS Lambda old runtimes: no updates to functions on deprecated runt
 imes
DESCRIPTION:AWS Lambda deprecated managed runtimes (Node.js 16/18/20/22\, P
 ython 3.8/3.9/3.10\, Ruby 3.2/3.3\, .NET 6/8\, Java 8\, Go 1.x\, provided\
 , provided.al2)\nVendor: Amazon Web Services\nAugust 31\, 2027: no updates
  to functions on deprecated runtimes\nWhat stops: From 2027-07-29 new func
 tions cannot use deprecated runtimes and from 2027-08-31 their code and co
 nfiguration cannot be updated\; existing functions can still be invoked.\n
 Data deleted: No. Functions are not deleted\; deprecated runtimes get no s
 ecurity patches\nWhere to move: Official: upgrade to a supported runtime (
 nodejs24.x\, python3.12-3.14\, java21/java25\, dotnet10\, provided.al2023)
 \; Move small glue or cron functions that are not worth upgrading to a wor
 kflow tool or another FaaS\nDetails and sources: https://workflowexit.com/
 shutdowns#aws-lambda-runtimes
URL:https://workflowexit.com/shutdowns#aws-lambda-runtimes
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:heroku-22-heroku-22-first-build-every-30-days-fails@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261101
DTEND;VALUE=DATE:20261102
SUMMARY:Heroku-22 stack: Heroku-22: first build every 30 days fails
DESCRIPTION:Heroku (sustaining-engineering mode) and the Heroku-22 stack\nV
 endor: Salesforce (Heroku)\nNovember 1\, 2026: Heroku-22: first build ever
 y 30 days fails\nWhat stops: Heroku-22 apps cannot be built or deployed fr
 om 2027-05-01 (they keep running)\; the platform gets no new features and 
 no Enterprise contracts for new customers.\nData deleted: No. Apps are not
  shut down\; Heroku has set no end-of-life date for the platform\nWhere to
  move: Official: upgrade apps to the Heroku-24 stack\; Longer term: Render
 \, Railway\, Fly.io\, a hyperscaler\, or self-hosting\; Heroku Scheduler j
 obs that are really automations can move to a workflow tool\nDetails and s
 ources: https://workflowexit.com/shutdowns#heroku-22
URL:https://workflowexit.com/shutdowns#heroku-22
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:heroku-22-heroku-22-first-build-every-7-days-fails@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270201
DTEND;VALUE=DATE:20270202
SUMMARY:Heroku-22 stack: Heroku-22: first build every 7 days fails
DESCRIPTION:Heroku (sustaining-engineering mode) and the Heroku-22 stack\nV
 endor: Salesforce (Heroku)\nFebruary 1\, 2027: Heroku-22: first build ever
 y 7 days fails\nWhat stops: Heroku-22 apps cannot be built or deployed fro
 m 2027-05-01 (they keep running)\; the platform gets no new features and n
 o Enterprise contracts for new customers.\nData deleted: No. Apps are not 
 shut down\; Heroku has set no end-of-life date for the platform\nWhere to 
 move: Official: upgrade apps to the Heroku-24 stack\; Longer term: Render\
 , Railway\, Fly.io\, a hyperscaler\, or self-hosting\; Heroku Scheduler jo
 bs that are really automations can move to a workflow tool\nDetails and so
 urces: https://workflowexit.com/shutdowns#heroku-22
URL:https://workflowexit.com/shutdowns#heroku-22
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:heroku-22-heroku-22-first-build-every-24-hours-fails@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270401
DTEND;VALUE=DATE:20270402
SUMMARY:Heroku-22 stack: Heroku-22: first build every 24 hours fails
DESCRIPTION:Heroku (sustaining-engineering mode) and the Heroku-22 stack\nV
 endor: Salesforce (Heroku)\nApril 1\, 2027: Heroku-22: first build every 2
 4 hours fails\nWhat stops: Heroku-22 apps cannot be built or deployed from
  2027-05-01 (they keep running)\; the platform gets no new features and no
  Enterprise contracts for new customers.\nData deleted: No. Apps are not s
 hut down\; Heroku has set no end-of-life date for the platform\nWhere to m
 ove: Official: upgrade apps to the Heroku-24 stack\; Longer term: Render\,
  Railway\, Fly.io\, a hyperscaler\, or self-hosting\; Heroku Scheduler job
 s that are really automations can move to a workflow tool\nDetails and sou
 rces: https://workflowexit.com/shutdowns#heroku-22
URL:https://workflowexit.com/shutdowns#heroku-22
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:heroku-22-heroku-22-end-of-life@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270430
DTEND;VALUE=DATE:20270501
SUMMARY:Heroku-22 stack: Heroku-22 end of life
DESCRIPTION:Heroku (sustaining-engineering mode) and the Heroku-22 stack\nV
 endor: Salesforce (Heroku)\nApril 30\, 2027: Heroku-22 end of life\nWhat s
 tops: Heroku-22 apps cannot be built or deployed from 2027-05-01 (they kee
 p running)\; the platform gets no new features and no Enterprise contracts
  for new customers.\nData deleted: No. Apps are not shut down\; Heroku has
  set no end-of-life date for the platform\nWhere to move: Official: upgrad
 e apps to the Heroku-24 stack\; Longer term: Render\, Railway\, Fly.io\, a
  hyperscaler\, or self-hosting\; Heroku Scheduler jobs that are really aut
 omations can move to a workflow tool\nDetails and sources: https://workflo
 wexit.com/shutdowns#heroku-22
URL:https://workflowexit.com/shutdowns#heroku-22
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:heroku-22-no-builds-or-deploys-on-heroku-22@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270501
DTEND;VALUE=DATE:20270502
SUMMARY:Heroku-22 stack: no builds or deploys on Heroku-22
DESCRIPTION:Heroku (sustaining-engineering mode) and the Heroku-22 stack\nV
 endor: Salesforce (Heroku)\nMay 1\, 2027: no builds or deploys on Heroku-2
 2\nWhat stops: Heroku-22 apps cannot be built or deployed from 2027-05-01 
 (they keep running)\; the platform gets no new features and no Enterprise 
 contracts for new customers.\nData deleted: No. Apps are not shut down\; H
 eroku has set no end-of-life date for the platform\nWhere to move: Officia
 l: upgrade apps to the Heroku-24 stack\; Longer term: Render\, Railway\, F
 ly.io\, a hyperscaler\, or self-hosting\; Heroku Scheduler jobs that are r
 eally automations can move to a workflow tool\nDetails and sources: https:
 //workflowexit.com/shutdowns#heroku-22
URL:https://workflowexit.com/shutdowns#heroku-22
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:auth0-rules-hooks-read-only@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20241118
DTEND;VALUE=DATE:20241119
SUMMARY:Auth0 Rules and Hooks: read-only
DESCRIPTION:Auth0 Rules and Hooks\nVendor: Okta (Auth0)\nNovember 18\, 2024
 : read-only\nWhat stops: Rules and Hooks stop running\, so login-pipeline 
 logic and the side effects they trigger (profile enrichment\, webhooks\, n
 otifications) stop.\nData deleted: Yes. Auth0 says Rules and Hooks are rem
 oved at end of life\; keep your own copy of the code\nWhere to move: Offic
 ial: Auth0 Actions (Migrate from Rules to Actions / Migrate from Hooks to 
 Actions guides)\; Move non-blocking side effects (CRM sync\, chat alerts) 
 to Auth0 log streams or webhooks handled by an integration tool\nDetails a
 nd sources: https://workflowexit.com/shutdowns#auth0-rules-hooks
URL:https://workflowexit.com/shutdowns#auth0-rules-hooks
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:auth0-rules-hooks-rules-and-hooks-stop-running-and-are-removed@workflow
 exit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261118
DTEND;VALUE=DATE:20261119
SUMMARY:Auth0 Rules and Hooks: Rules and Hooks stop running and are removed
DESCRIPTION:Auth0 Rules and Hooks\nVendor: Okta (Auth0)\nNovember 18\, 2026
 : Rules and Hooks stop running and are removed\nWhat stops: Rules and Hook
 s stop running\, so login-pipeline logic and the side effects they trigger
  (profile enrichment\, webhooks\, notifications) stop.\nData deleted: Yes.
  Auth0 says Rules and Hooks are removed at end of life\; keep your own cop
 y of the code\nWhere to move: Official: Auth0 Actions (Migrate from Rules 
 to Actions / Migrate from Hooks to Actions guides)\; Move non-blocking sid
 e effects (CRM sync\, chat alerts) to Auth0 log streams or webhooks handle
 d by an integration tool\nDetails and sources: https://workflowexit.com/sh
 utdowns#auth0-rules-hooks
URL:https://workflowexit.com/shutdowns#auth0-rules-hooks
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:claude-sonnet-4-5-retired-requests-fail@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261130
DTEND;VALUE=DATE:20261201
SUMMARY:Claude Sonnet 4.5: retired\, requests fail
DESCRIPTION:Claude Sonnet 4.5 (claude-sonnet-4-5-20250929) on the Claude AP
 I\nVendor: Anthropic\nNovember 30\, 2026: retired\, requests fail\nWhat st
 ops: Requests to claude-sonnet-4-5-20250929 fail on Anthropic-operated pla
 tforms.\nData deleted: No. Model retirement only\nWhere to move: Official:
  claude-sonnet-5-5\; Re-test prompts and tool calls\; Claude 4.7 and later
  models return a 400 error for a non-default temperature\, top_p or top_k\
 nDetails and sources: https://workflowexit.com/shutdowns#claude-sonnet-4-5
URL:https://workflowexit.com/shutdowns#claude-sonnet-4-5
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:prisma-accelerate-accelerate-retired@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:Prisma Accelerate: Accelerate retired
DESCRIPTION:Prisma Accelerate (connection pooling and query caching)\nVendo
 r: Prisma\nDecember 1\, 2026: Accelerate retired\nWhat stops: Accelerate i
 s retired\, including Prisma Postgres connections routed through it\; quer
 y caching (cacheStrategy) has no replacement.\nData deleted: No. Prisma sa
 ys your database\, your data and your plan stay as they are\; only the con
 nection changes\nWhere to move: Official: switch to a pooled connection or
  the serverless driver\; Official: keep your own database and connect with
 out Accelerate\, or move to Prisma Postgres\; Remove cacheStrategy from qu
 eries before switching\nDetails and sources: https://workflowexit.com/shut
 downs#prisma-accelerate
URL:https://workflowexit.com/shutdowns#prisma-accelerate
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:exchange-smtp-basic-auth-basic-auth-for-smtp-auth-off-by-default@workfl
 owexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:Exchange Online SMTP basic auth: Basic auth for SMTP AUTH off by de
 fault (December 2026\, exact day not announced)
DESCRIPTION:Exchange Online SMTP AUTH with Basic authentication (username/p
 assword client submission)\nVendor: Microsoft\nDecember 2026: Basic auth f
 or SMTP AUTH off by default (admins can re-enable it for existing tenants\
 ; new tenants can't use it)\nWhat stops: Apps\, scripts\, devices and auto
 mations that send mail through Exchange Online SMTP AUTH with a username a
 nd password are rejected unless an admin re-enables Basic auth.\nData dele
 ted: No. Authentication change only\nWhere to move: Official: OAuth 2.0 fo
 r SMTP AUTH\; Microsoft Graph sendMail\; A third-party SMTP relay (Amazon 
 SES\, SendGrid\, Mailgun)\nDetails and sources: https://workflowexit.com/s
 hutdowns#exchange-smtp-basic-auth
URL:https://workflowexit.com/shutdowns#exchange-smtp-basic-auth
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:google-custom-search-api-new-engines-limited-to-50-sites@workflowexit.c
 om
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260120
DTEND;VALUE=DATE:20260121
SUMMARY:Google Custom Search JSON API: new engines limited to 50 sites
DESCRIPTION:Google Custom Search JSON API and the Programmable Search Engin
 e option to search the entire web\nVendor: Google\nJanuary 20\, 2026: new 
 engines limited to 50 sites\nWhat stops: The Custom Search JSON API (alrea
 dy closed to new customers) stops for existing customers\, and existing en
 gines lose whole-web search.\nData deleted: No. No user data involved\; th
 e endpoint stops serving results\nWhere to move: Official: Vertex AI Searc
 h (up to 50 domains) or contact Google about its full web search solution\
 ; Third-party web search APIs (Brave Search API\, SerpAPI\, Tavily\, Exa)\
 ; Search grounding built into model APIs (Gemini\, OpenAI\, Anthropic web 
 search tools)\nDetails and sources: https://workflowexit.com/shutdowns#goo
 gle-custom-search-api
URL:https://workflowexit.com/shutdowns#google-custom-search-api
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:google-custom-search-api-json-api-stops-for-existing-customers@workflow
 exit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270101
DTEND;VALUE=DATE:20270102
SUMMARY:Google Custom Search JSON API: JSON API stops for existing customer
 s
DESCRIPTION:Google Custom Search JSON API and the Programmable Search Engin
 e option to search the entire web\nVendor: Google\nJanuary 1\, 2027: JSON 
 API stops for existing customers (existing engines also lose whole-web sea
 rch)\nWhat stops: The Custom Search JSON API (already closed to new custom
 ers) stops for existing customers\, and existing engines lose whole-web se
 arch.\nData deleted: No. No user data involved\; the endpoint stops servin
 g results\nWhere to move: Official: Vertex AI Search (up to 50 domains) or
  contact Google about its full web search solution\; Third-party web searc
 h APIs (Brave Search API\, SerpAPI\, Tavily\, Exa)\; Search grounding buil
 t into model APIs (Gemini\, OpenAI\, Anthropic web search tools)\nDetails 
 and sources: https://workflowexit.com/shutdowns#google-custom-search-api
URL:https://workflowexit.com/shutdowns#google-custom-search-api
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:zendesk-legacy-ai-agents-legacy-experience-in-maintenance-mode@workflow
 exit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260831
DTEND;VALUE=DATE:20260901
SUMMARY:Zendesk legacy AI agents: legacy experience in maintenance mode
DESCRIPTION:Zendesk AI agents: Essential and legacy AI agent functionality 
 (bot builder\, answers\, intents)\nVendor: Zendesk\nAugust 31\, 2026: lega
 cy experience in maintenance mode\nWhat stops: The Essential and legacy bo
 t experiences are removed\; Zendesk migrates bots that customers have not 
 moved to the upgraded AI agent experience\, with some exceptions.\nData de
 leted: No. Bots are migrated rather than deleted (Zendesk notes exceptions
 )\nWhere to move: Official: migrate to the upgraded AI agent experience (c
 apabilities formerly in the AI agents - Advanced add-on) using the Zendesk
  per-feature migration guides\; Zendesk Professional Services\nDetails and
  sources: https://workflowexit.com/shutdowns#zendesk-legacy-ai-agents
URL:https://workflowexit.com/shutdowns#zendesk-legacy-ai-agents
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:zendesk-legacy-ai-agents-essential-ai-agents-migrated@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270101
DTEND;VALUE=DATE:20270102
SUMMARY:Zendesk legacy AI agents: Essential AI agents migrated (January 202
 7\, exact day not announced)
DESCRIPTION:Zendesk AI agents: Essential and legacy AI agent functionality 
 (bot builder\, answers\, intents)\nVendor: Zendesk\nJanuary 2027: Essentia
 l AI agents migrated\nWhat stops: The Essential and legacy bot experiences
  are removed\; Zendesk migrates bots that customers have not moved to the 
 upgraded AI agent experience\, with some exceptions.\nData deleted: No. Bo
 ts are migrated rather than deleted (Zendesk notes exceptions)\nWhere to m
 ove: Official: migrate to the upgraded AI agent experience (capabilities f
 ormerly in the AI agents - Advanced add-on) using the Zendesk per-feature 
 migration guides\; Zendesk Professional Services\nDetails and sources: htt
 ps://workflowexit.com/shutdowns#zendesk-legacy-ai-agents
URL:https://workflowexit.com/shutdowns#zendesk-legacy-ai-agents
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:zendesk-legacy-ai-agents-legacy-ai-agents-migrated@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270201
DTEND;VALUE=DATE:20270202
SUMMARY:Zendesk legacy AI agents: legacy AI agents migrated (February 2027\
 , exact day not announced)
DESCRIPTION:Zendesk AI agents: Essential and legacy AI agent functionality 
 (bot builder\, answers\, intents)\nVendor: Zendesk\nFebruary 2027: legacy 
 AI agents migrated\nWhat stops: The Essential and legacy bot experiences a
 re removed\; Zendesk migrates bots that customers have not moved to the up
 graded AI agent experience\, with some exceptions.\nData deleted: No. Bots
  are migrated rather than deleted (Zendesk notes exceptions)\nWhere to mov
 e: Official: migrate to the upgraded AI agent experience (capabilities for
 merly in the AI agents - Advanced add-on) using the Zendesk per-feature mi
 gration guides\; Zendesk Professional Services\nDetails and sources: https
 ://workflowexit.com/shutdowns#zendesk-legacy-ai-agents
URL:https://workflowexit.com/shutdowns#zendesk-legacy-ai-agents
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-audio-models-text-to-speech-models-stop-working@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270106
DTEND;VALUE=DATE:20270107
SUMMARY:OpenAI speech and audio models: text-to-speech models stop working
DESCRIPTION:OpenAI speech\, transcription and audio/realtime models (tts-1\
 , tts-1-hd\, whisper-1\, gpt-4o-transcribe\, gpt-realtime\, gpt-audio and 
 variants)\nVendor: OpenAI\nJanuary 6\, 2027: text-to-speech models stop wo
 rking (tts-1\, tts-1-hd\, gpt-4o-mini-tts-2025-03-20\, gpt-4o-mini-tts-202
 5-12-15)\nWhat stops: Text-to-speech\, transcription/translation and older
  realtime/audio models are removed from the API on these dates.\nData dele
 ted: No. Model retirement only\nWhere to move: Official: gpt-realtime-2.1-
 mini (TTS)\; gpt-live-transcribe or gpt-transcribe (transcription)\; v1/re
 altime/translations\; gpt-realtime-2.1 or gpt-audio-1.5 (realtime/audio)\;
  Other speech APIs (Deepgram\, AssemblyAI\, ElevenLabs\, Google Cloud\, Az
 ure AI Speech)\nDetails and sources: https://workflowexit.com/shutdowns#op
 enai-audio-models
URL:https://workflowexit.com/shutdowns#openai-audio-models
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-audio-models-realtime-and-audio-models-stop-working@workflowexit
 .com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270120
DTEND;VALUE=DATE:20270121
SUMMARY:OpenAI speech and audio models: realtime and audio models stop work
 ing
DESCRIPTION:OpenAI speech\, transcription and audio/realtime models (tts-1\
 , tts-1-hd\, whisper-1\, gpt-4o-transcribe\, gpt-realtime\, gpt-audio and 
 variants)\nVendor: OpenAI\nJanuary 20\, 2027: realtime and audio models st
 op working (gpt-realtime\, gpt-audio\, gpt-4o-audio\, gpt-4o-realtime and 
 their mini variants)\nWhat stops: Text-to-speech\, transcription/translati
 on and older realtime/audio models are removed from the API on these dates
 .\nData deleted: No. Model retirement only\nWhere to move: Official: gpt-r
 ealtime-2.1-mini (TTS)\; gpt-live-transcribe or gpt-transcribe (transcript
 ion)\; v1/realtime/translations\; gpt-realtime-2.1 or gpt-audio-1.5 (realt
 ime/audio)\; Other speech APIs (Deepgram\, AssemblyAI\, ElevenLabs\, Googl
 e Cloud\, Azure AI Speech)\nDetails and sources: https://workflowexit.com/
 shutdowns#openai-audio-models
URL:https://workflowexit.com/shutdowns#openai-audio-models
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-audio-models-transcription-models-stop-working@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270226
DTEND;VALUE=DATE:20270227
SUMMARY:OpenAI speech and audio models: transcription models stop working
DESCRIPTION:OpenAI speech\, transcription and audio/realtime models (tts-1\
 , tts-1-hd\, whisper-1\, gpt-4o-transcribe\, gpt-realtime\, gpt-audio and 
 variants)\nVendor: OpenAI\nFebruary 26\, 2027: transcription models stop w
 orking (whisper-1\, gpt-4o-transcribe\, gpt-4o-mini-transcribe\, gpt-4o-tr
 anscribe-diarize and /v1/audio/translations)\nWhat stops: Text-to-speech\,
  transcription/translation and older realtime/audio models are removed fro
 m the API on these dates.\nData deleted: No. Model retirement only\nWhere 
 to move: Official: gpt-realtime-2.1-mini (TTS)\; gpt-live-transcribe or gp
 t-transcribe (transcription)\; v1/realtime/translations\; gpt-realtime-2.1
  or gpt-audio-1.5 (realtime/audio)\; Other speech APIs (Deepgram\, Assembl
 yAI\, ElevenLabs\, Google Cloud\, Azure AI Speech)\nDetails and sources: h
 ttps://workflowexit.com/shutdowns#openai-audio-models
URL:https://workflowexit.com/shutdowns#openai-audio-models
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt-4o-gpt-4-1-stops-working-fine-tunes-included@workflowexit.co
 m
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270114
DTEND;VALUE=DATE:20270115
SUMMARY:OpenAI GPT-4o and GPT-4.1: stops working\, fine-tunes included
DESCRIPTION:OpenAI GPT-4o\, GPT-4o mini\, GPT-4.1 and GPT-4.1 mini\nVendor:
  OpenAI\nJanuary 14\, 2027: stops working\, fine-tunes included\nWhat stop
 s: gpt-4o-2024-08-06\, gpt-4o-2024-11-20\, gpt-4o-mini-2024-07-18\, gpt-4.
 1-2025-04-14 and gpt-4.1-mini-2025-04-14\, plus fine-tunes on them\, are r
 emoved from the API.\nData deleted: Not announced. Fine-tuned versions fol
 low the base-model shutdown\; nothing is said about training files\nWhere 
 to move: Official: gpt-6-luna\; Re-test structured output and function cal
 ling before switching\; Or another provider model\nDetails and sources: ht
 tps://workflowexit.com/shutdowns#openai-gpt-4o-gpt-4-1
URL:https://workflowexit.com/shutdowns#openai-gpt-4o-gpt-4-1
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:atlassian-connect-no-connect-app-updates-or-new-private-installs@workfl
 owexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260331
DTEND;VALUE=DATE:20260401
SUMMARY:Atlassian Connect: no Connect app updates or new private installs
DESCRIPTION:Atlassian Connect framework (Jira and Confluence Cloud apps\, i
 ncluding private/custom Connect apps)\nVendor: Atlassian\nMarch 31\, 2026:
  no Connect app updates or new private installs\nWhat stops: After 2027-01
 -31 Connect gets only critical security fixes and Atlassian expects breaka
 ges to grow\; apps are not switched off on that date.\nData deleted: No. N
 o deletion announced\; apps degrade over time\nWhere to move: Official: mi
 grate or rebuild the app on Forge\; For simple webhook/REST integrations: 
 Jira/Confluence webhooks and REST API driven from an integration tool\nDet
 ails and sources: https://workflowexit.com/shutdowns#atlassian-connect
URL:https://workflowexit.com/shutdowns#atlassian-connect
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:atlassian-connect-connect-end-of-support@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270131
DTEND;VALUE=DATE:20270201
SUMMARY:Atlassian Connect: Connect end of support
DESCRIPTION:Atlassian Connect framework (Jira and Confluence Cloud apps\, i
 ncluding private/custom Connect apps)\nVendor: Atlassian\nJanuary 31\, 202
 7: Connect end of support\nWhat stops: After 2027-01-31 Connect gets only 
 critical security fixes and Atlassian expects breakages to grow\; apps are
  not switched off on that date.\nData deleted: No. No deletion announced\;
  apps degrade over time\nWhere to move: Official: migrate or rebuild the a
 pp on Forge\; For simple webhook/REST integrations: Jira/Confluence webhoo
 ks and REST API driven from an integration tool\nDetails and sources: http
 s://workflowexit.com/shutdowns#atlassian-connect
URL:https://workflowexit.com/shutdowns#atlassian-connect
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:twilio-notify-end-of-life-for-existing-customers@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270131
DTEND;VALUE=DATE:20270201
SUMMARY:Twilio Notify: end of life for existing customers
DESCRIPTION:Twilio Notify\nVendor: Twilio\nJanuary 31\, 2027: end of life f
 or existing customers\nWhat stops: The Notify API (bulk SMS fan-out and pu
 sh notifications through bindings) stops for existing customers.\nData del
 eted: Not announced. Twilio does not say what happens to Notify bindings o
 r other stored data\nWhere to move: Official: Programmable Messaging/SMS A
 PI (with message scheduling) or the Bulk Messaging API for SMS\; Official:
  Verify (push authentication)\, Conversations\, Segment with push partners
 \; Push API private beta\; Notification services such as Courier\, Knock\,
  OneSignal\nDetails and sources: https://workflowexit.com/shutdowns#twilio
 -notify
URL:https://workflowexit.com/shutdowns#twilio-notify
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:firebase-studio-no-new-workspaces-or-signups@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260622
DTEND;VALUE=DATE:20260623
SUMMARY:Firebase Studio: no new workspaces or signups
DESCRIPTION:Firebase Studio\nVendor: Google\nJune 22\, 2026: no new workspa
 ces or signups\nWhat stops: Firebase Studio workspaces stop\; core Firebas
 e services (Cloud Firestore\, Authentication\, App Hosting) keep working.\
 nData deleted: Yes. All remaining Firebase Studio data is permanently dele
 ted on 2027-03-22 and cannot be recovered\nWhere to move: Official: Google
  Antigravity (code-first) or Google AI Studio (browser prototyping)\; Offi
 cial export: the Move now button or npx firebase-tools@latest studio:expor
 t PATH\; Other cloud IDEs or AI app builders (GitHub Codespaces\, Replit)\
 nDetails and sources: https://workflowexit.com/shutdowns#firebase-studio
URL:https://workflowexit.com/shutdowns#firebase-studio
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:firebase-studio-shut-down-data-deleted@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270322
DTEND;VALUE=DATE:20270323
SUMMARY:Firebase Studio: shut down\, data deleted
DESCRIPTION:Firebase Studio\nVendor: Google\nMarch 22\, 2027: shut down\, d
 ata deleted\nWhat stops: Firebase Studio workspaces stop\; core Firebase s
 ervices (Cloud Firestore\, Authentication\, App Hosting) keep working.\nDa
 ta deleted: Yes. All remaining Firebase Studio data is permanently deleted
  on 2027-03-22 and cannot be recovered\nWhere to move: Official: Google An
 tigravity (code-first) or Google AI Studio (browser prototyping)\; Officia
 l export: the Move now button or npx firebase-tools@latest studio:export P
 ATH\; Other cloud IDEs or AI app builders (GitHub Codespaces\, Replit)\nDe
 tails and sources: https://workflowexit.com/shutdowns#firebase-studio
URL:https://workflowexit.com/shutdowns#firebase-studio
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:amazon-sp-api-v0-orders-api-v0-operations-removed@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270327
DTEND;VALUE=DATE:20270328
SUMMARY:Amazon SP-API Orders and Finances v0: Orders API v0 operations remo
 ved
DESCRIPTION:Amazon Selling Partner API: Orders API v0 and Finances API v0 o
 perations\nVendor: Amazon\nMarch 27\, 2027: Orders API v0 operations remov
 ed (getOrders\, getOrder\, getOrderBuyerInfo\, getOrderAddress\, getOrderI
 tems\, getOrderItemsBuyerInfo)\nWhat stops: Calls to these v0 operations s
 top working\, breaking order and settlement syncs that still use them.\nDa
 ta deleted: No. API removal only\nWhere to move: Official: move to the cur
 rent Orders and Finances API versions per the SP-API deprecation schedule 
 and migration guides\; Update Amazon Seller steps in Make\, Zapier\, n8n o
 r custom code\nDetails and sources: https://workflowexit.com/shutdowns#ama
 zon-sp-api-v0
URL:https://workflowexit.com/shutdowns#amazon-sp-api-v0
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:amazon-sp-api-v0-finances-api-v0-operations-removed@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270827
DTEND;VALUE=DATE:20270828
SUMMARY:Amazon SP-API Orders and Finances v0: Finances API v0 operations re
 moved
DESCRIPTION:Amazon Selling Partner API: Orders API v0 and Finances API v0 o
 perations\nVendor: Amazon\nAugust 27\, 2027: Finances API v0 operations re
 moved (listFinancialEvents\, listFinancialEventsByGroupId\, listFinancialE
 ventsByOrderId)\nWhat stops: Calls to these v0 operations stop working\, b
 reaking order and settlement syncs that still use them.\nData deleted: No.
  API removal only\nWhere to move: Official: move to the current Orders and
  Finances API versions per the SP-API deprecation schedule and migration g
 uides\; Update Amazon Seller steps in Make\, Zapier\, n8n or custom code\n
 Details and sources: https://workflowexit.com/shutdowns#amazon-sp-api-v0
URL:https://workflowexit.com/shutdowns#amazon-sp-api-v0
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:pipedream-workflows-signups-and-new-subscriptions-closed@workflowexit.c
 om
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260930
DTEND;VALUE=DATE:20261001
SUMMARY:Pipedream Workflows: signups and new subscriptions closed
DESCRIPTION:Pipedream Workflows (and String)\nVendor: Pipedream (Workday)\n
 September 30\, 2026: signups and new subscriptions closed\nWhat stops: Eve
 ry Pipedream workflow and String stops running. Pipedream Connect (Connect
  API\, MCP servers\, API Proxy) is not affected.\nData deleted: Yes. All W
 orkflows data is permanently deleted\, including credentials and OAuth tok
 ens of connected accounts. Data store records and File Store files are not
  in the official export\, so copy them first\nWhere to move: Official: the
  Export Workflows tool (JSON\, secret values redacted)\; n8n (cloud or sel
 f-hosted)\; Make\, Zapier\, Activepieces\, Windmill or plain serverless co
 de\nMigration guide: https://workflowexit.com/pipedream-to-n8n\nDetails an
 d sources: https://workflowexit.com/shutdowns#pipedream-workflows
URL:https://workflowexit.com/shutdowns#pipedream-workflows
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:pipedream-workflows-stops-working@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270331
DTEND;VALUE=DATE:20270401
SUMMARY:Pipedream Workflows: stops working
DESCRIPTION:Pipedream Workflows (and String)\nVendor: Pipedream (Workday)\n
 March 31\, 2027: stops working (subscriptions cancelled with a prorated re
 fund)\nWhat stops: Every Pipedream workflow and String stops running. Pipe
 dream Connect (Connect API\, MCP servers\, API Proxy) is not affected.\nDa
 ta deleted: Yes. All Workflows data is permanently deleted\, including cre
 dentials and OAuth tokens of connected accounts. Data store records and Fi
 le Store files are not in the official export\, so copy them first\nWhere 
 to move: Official: the Export Workflows tool (JSON\, secret values redacte
 d)\; n8n (cloud or self-hosted)\; Make\, Zapier\, Activepieces\, Windmill 
 or plain serverless code\nMigration guide: https://workflowexit.com/pipedr
 eam-to-n8n\nDetails and sources: https://workflowexit.com/shutdowns#pipedr
 eam-workflows
URL:https://workflowexit.com/shutdowns#pipedream-workflows
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:pipedream-workflows-all-data-deleted@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270430
DTEND;VALUE=DATE:20270501
SUMMARY:Pipedream Workflows: all data deleted
DESCRIPTION:Pipedream Workflows (and String)\nVendor: Pipedream (Workday)\n
 April 30\, 2027: all data deleted\nWhat stops: Every Pipedream workflow an
 d String stops running. Pipedream Connect (Connect API\, MCP servers\, API
  Proxy) is not affected.\nData deleted: Yes. All Workflows data is permane
 ntly deleted\, including credentials and OAuth tokens of connected account
 s. Data store records and File Store files are not in the official export\
 , so copy them first\nWhere to move: Official: the Export Workflows tool (
 JSON\, secret values redacted)\; n8n (cloud or self-hosted)\; Make\, Zapie
 r\, Activepieces\, Windmill or plain serverless code\nMigration guide: htt
 ps://workflowexit.com/pipedream-to-n8n\nDetails and sources: https://workf
 lowexit.com/shutdowns#pipedream-workflows
URL:https://workflowexit.com/shutdowns#pipedream-workflows
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:exchange-ews-deadline-to-opt-in@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260801
DTEND;VALUE=DATE:20260802
SUMMARY:Exchange Web Services (EWS): deadline to opt in (August 2026\, exac
 t day not announced)
DESCRIPTION:Exchange Web Services (EWS) in Exchange Online\nVendor: Microso
 ft\nAugust 2026: deadline to opt in (set EWSEnabled=True and an AppID allo
 w list)\nWhat stops: All EWS requests to Exchange Online are blocked\; on-
 premises Exchange Server is not affected.\nData deleted: No. API shutdown 
 only\; mailbox data stays\nWhere to move: Official: Microsoft Graph\; Upda
 te or replace third-party tools that still use EWS (backup\, archiving\, C
 RM and email sync)\; Rebuild in-house EWS scripts as Graph-based automatio
 ns (n8n Microsoft Outlook node\, Power Automate)\nDetails and sources: htt
 ps://workflowexit.com/shutdowns#exchange-ews
URL:https://workflowexit.com/shutdowns#exchange-ews
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:exchange-ews-ews-off-by-default@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20261001
DTEND;VALUE=DATE:20261002
SUMMARY:Exchange Web Services (EWS): EWS off by default
DESCRIPTION:Exchange Web Services (EWS) in Exchange Online\nVendor: Microso
 ft\nOctober 1\, 2026: EWS off by default (for tenants that did not opt in\
 ; admins can re-enable it)\nWhat stops: All EWS requests to Exchange Onlin
 e are blocked\; on-premises Exchange Server is not affected.\nData deleted
 : No. API shutdown only\; mailbox data stays\nWhere to move: Official: Mic
 rosoft Graph\; Update or replace third-party tools that still use EWS (bac
 kup\, archiving\, CRM and email sync)\; Rebuild in-house EWS scripts as Gr
 aph-based automations (n8n Microsoft Outlook node\, Power Automate)\nDetai
 ls and sources: https://workflowexit.com/shutdowns#exchange-ews
URL:https://workflowexit.com/shutdowns#exchange-ews
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:exchange-ews-ews-permanently-disabled@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270401
DTEND;VALUE=DATE:20270402
SUMMARY:Exchange Web Services (EWS): EWS permanently disabled
DESCRIPTION:Exchange Web Services (EWS) in Exchange Online\nVendor: Microso
 ft\nApril 1\, 2027: EWS permanently disabled\nWhat stops: All EWS requests
  to Exchange Online are blocked\; on-premises Exchange Server is not affec
 ted.\nData deleted: No. API shutdown only\; mailbox data stays\nWhere to m
 ove: Official: Microsoft Graph\; Update or replace third-party tools that 
 still use EWS (backup\, archiving\, CRM and email sync)\; Rebuild in-house
  EWS scripts as Graph-based automations (n8n Microsoft Outlook node\, Powe
 r Automate)\nDetails and sources: https://workflowexit.com/shutdowns#excha
 nge-ews
URL:https://workflowexit.com/shutdowns#exchange-ews
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:deno-deploy-deploy-classic-and-subhosting-v1-api-shut-down@workflowexit
 .com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260720
DTEND;VALUE=DATE:20260721
SUMMARY:Deno Deploy: Deploy Classic and Subhosting v1 API shut down
DESCRIPTION:Deno Deploy (plus Deno Deploy Classic and the Subhosting v1 API
 )\nVendor: Deno (team joining Cloudflare)\nJuly 20\, 2026: Deploy Classic 
 and Subhosting v1 API shut down\nWhat stops: The Deno Deploy hosting servi
 ce and everything running on it stop\; the open-source Deno runtime gets o
 ne more year of fixes\, then official development ends.\nData deleted: Not
  announced. The announcement does not say how long hosted data (for exampl
 e Deno KV) stays exportable\nWhere to move: Official: Cloudflare Workers (
 migration support for paying customers)\; Other serverless hosts (Vercel\,
  Netlify\, Fly.io\, AWS Lambda)\; Cron and webhook scripts can move to a w
 orkflow tool\nDetails and sources: https://workflowexit.com/shutdowns#deno
 -deploy
URL:https://workflowexit.com/shutdowns#deno-deploy
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:deno-deploy-deno-deploy-shuts-down@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270401
DTEND;VALUE=DATE:20270402
SUMMARY:Deno Deploy: Deno Deploy shuts down (April 2027\, exact day not ann
 ounced)
DESCRIPTION:Deno Deploy (plus Deno Deploy Classic and the Subhosting v1 API
 )\nVendor: Deno (team joining Cloudflare)\nApril 2027: Deno Deploy shuts d
 own (six months after the 2026-10-09 announcement\; exact day not publishe
 d)\nWhat stops: The Deno Deploy hosting service and everything running on 
 it stop\; the open-source Deno runtime gets one more year of fixes\, then 
 official development ends.\nData deleted: Not announced. The announcement 
 does not say how long hosted data (for example Deno KV) stays exportable\n
 Where to move: Official: Cloudflare Workers (migration support for paying 
 customers)\; Other serverless hosts (Vercel\, Netlify\, Fly.io\, AWS Lambd
 a)\; Cron and webhook scripts can move to a workflow tool\nDetails and sou
 rces: https://workflowexit.com/shutdowns#deno-deploy
URL:https://workflowexit.com/shutdowns#deno-deploy
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:deno-deploy-official-deno-runtime-development-ends@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20271001
DTEND;VALUE=DATE:20271002
SUMMARY:Deno Deploy: official Deno runtime development ends (October 2027\,
  exact day not announced)
DESCRIPTION:Deno Deploy (plus Deno Deploy Classic and the Subhosting v1 API
 )\nVendor: Deno (team joining Cloudflare)\nOctober 2027: official Deno run
 time development ends (after a year of monthly bug-fix and security releas
 es)\nWhat stops: The Deno Deploy hosting service and everything running on
  it stop\; the open-source Deno runtime gets one more year of fixes\, then
  official development ends.\nData deleted: Not announced. The announcement
  does not say how long hosted data (for example Deno KV) stays exportable\
 nWhere to move: Official: Cloudflare Workers (migration support for paying
  customers)\; Other serverless hosts (Vercel\, Netlify\, Fly.io\, AWS Lamb
 da)\; Cron and webhook scripts can move to a workflow tool\nDetails and so
 urces: https://workflowexit.com/shutdowns#deno-deploy
URL:https://workflowexit.com/shutdowns#deno-deploy
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:opsgenie-end-of-sale@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20250604
DTEND;VALUE=DATE:20250605
SUMMARY:Opsgenie: end of sale
DESCRIPTION:Atlassian Opsgenie\nVendor: Atlassian\nJune 4\, 2025: end of sa
 le\nWhat stops: Opsgenie (alerting\, on-call\, escalations and its APIs/in
 tegrations) is shut off and no longer accessible.\nData deleted: Yes. Data
  not moved to Jira Service Management (or downloaded) is deleted on 2027-0
 4-05\nWhere to move: Official: Jira Service Management (or Compass\, which
  lacks stakeholder management)\; PagerDuty\, incident.io\, Better Stack\, 
 Squadcast\nDetails and sources: https://workflowexit.com/shutdowns#opsgeni
 e
URL:https://workflowexit.com/shutdowns#opsgenie
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:opsgenie-shut-down-data-deleted@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270405
DTEND;VALUE=DATE:20270406
SUMMARY:Opsgenie: shut down\, data deleted
DESCRIPTION:Atlassian Opsgenie\nVendor: Atlassian\nApril 5\, 2027: shut dow
 n\, data deleted\nWhat stops: Opsgenie (alerting\, on-call\, escalations a
 nd its APIs/integrations) is shut off and no longer accessible.\nData dele
 ted: Yes. Data not moved to Jira Service Management (or downloaded) is del
 eted on 2027-04-05\nWhere to move: Official: Jira Service Management (or C
 ompass\, which lacks stakeholder management)\; PagerDuty\, incident.io\, B
 etter Stack\, Squadcast\nDetails and sources: https://workflowexit.com/shu
 tdowns#opsgenie
URL:https://workflowexit.com/shutdowns#opsgenie
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:zendesk-sell-retired-data-deletion-starts@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20270831
DTEND;VALUE=DATE:20270901
SUMMARY:Zendesk Sell: retired\, data deletion starts
DESCRIPTION:Zendesk Sell (sales CRM) and its mobile app\nVendor: Zendesk\nA
 ugust 31\, 2027: retired\, data deletion starts\nWhat stops: Zendesk Sell 
 and its mobile app stop working.\nData deleted: Yes. Data is deleted when 
 the subscription ends or from 2027-08-31\, whichever comes first\; activit
 y history\, appointments\, emails\, call logs and documents cannot be expo
 rted\nWhere to move: Official partner: Pipedrive (migration tools\, native
  Zendesk integration)\; Other CRMs (HubSpot\, Salesforce\, Zoho CRM)\; Exp
 ort leads\, contacts\, deals\, notes\, tasks and smart lists via Settings 
 > Data > Export (CSV)\nDetails and sources: https://workflowexit.com/shutd
 owns#zendesk-sell
URL:https://workflowexit.com/shutdowns#zendesk-sell
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:flowise-code-freeze@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260729
DTEND;VALUE=DATE:20260730
SUMMARY:Flowise: code freeze
DESCRIPTION:Flowise (open-source visual LLM/agent builder)\nVendor: Flowise
 AI (Workday)\nJuly 29\, 2026: code freeze\nWhat stops: Official developmen
 t\, fixes and security patches have ended\; self-hosted installs keep runn
 ing without upstream updates.\nData deleted: Not announced. Self-hosted da
 ta stays where it is\; Flowise has published no Flowise Cloud shutdown or 
 deletion date\nWhere to move: Official: fork the Apache-2.0 repo and maint
 ain it\, or use a community fork\; n8n (AI Agent and LangChain nodes)\; La
 ngflow\, Dify\nDetails and sources: https://workflowexit.com/shutdowns#flo
 wise
URL:https://workflowexit.com/shutdowns#flowise
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:flowise-repo-archived@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260810
DTEND;VALUE=DATE:20260811
SUMMARY:Flowise: repo archived
DESCRIPTION:Flowise (open-source visual LLM/agent builder)\nVendor: Flowise
 AI (Workday)\nAugust 10\, 2026: repo archived (npm packages and Docker ima
 ges marked deprecated)\nWhat stops: Official development\, fixes and secur
 ity patches have ended\; self-hosted installs keep running without upstrea
 m updates.\nData deleted: Not announced. Self-hosted data stays where it i
 s\; Flowise has published no Flowise Cloud shutdown or deletion date\nWher
 e to move: Official: fork the Apache-2.0 repo and maintain it\, or use a c
 ommunity fork\; n8n (AI Agent and LangChain nodes)\; Langflow\, Dify\nDeta
 ils and sources: https://workflowexit.com/shutdowns#flowise
URL:https://workflowexit.com/shutdowns#flowise
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:flowise-end-of-life@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260831
DTEND;VALUE=DATE:20260901
SUMMARY:Flowise: end of life
DESCRIPTION:Flowise (open-source visual LLM/agent builder)\nVendor: Flowise
 AI (Workday)\nAugust 31\, 2026: end of life\nWhat stops: Official developm
 ent\, fixes and security patches have ended\; self-hosted installs keep ru
 nning without upstream updates.\nData deleted: Not announced. Self-hosted 
 data stays where it is\; Flowise has published no Flowise Cloud shutdown o
 r deletion date\nWhere to move: Official: fork the Apache-2.0 repo and mai
 ntain it\, or use a community fork\; n8n (AI Agent and LangChain nodes)\; 
 Langflow\, Dify\nDetails and sources: https://workflowexit.com/shutdowns#f
 lowise
URL:https://workflowexit.com/shutdowns#flowise
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:openai-assistants-api-removed-from-the-api@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260826
DTEND;VALUE=DATE:20260827
SUMMARY:OpenAI Assistants API: removed from the API
DESCRIPTION:OpenAI Assistants API\nVendor: OpenAI\nAugust 26\, 2026: remove
 d from the API\nWhat stops: The Assistants API (assistants\, threads\, run
 s) has been removed\, so automations built on assistant IDs no longer work
 .\nData deleted: Not announced. The OpenAI notice does not say whether sto
 red threads or files can still be retrieved\nWhere to move: Official: Resp
 onses API plus Conversations API (Assistants-to-Conversations migration gu
 ide)\; Agents SDK\; Rebuild as an agent in n8n (AI Agent node) or Make\nDe
 tails and sources: https://workflowexit.com/shutdowns#openai-assistants-ap
 i
URL:https://workflowexit.com/shutdowns#openai-assistants-api
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:teams-office-365-connectors-final-retirement-rollout-starts@workflowexi
 t.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260518
DTEND;VALUE=DATE:20260519
SUMMARY:Teams Office 365 connectors: final retirement rollout starts
DESCRIPTION:Office 365 Connectors in Microsoft Teams (including Incoming We
 bhook)\nVendor: Microsoft\nMay 18\, 2026: final retirement rollout starts\
 nWhat stops: Messages sent to Teams through Office 365 Connectors\, includ
 ing Incoming Webhook URLs\, are no longer delivered.\nData deleted: No. Pa
 st channel messages stay\; only delivery stops\nWhere to move: Official: W
 orkflows app in Teams (Power Automate) with Workflows webhooks\; A Teams b
 ot or Microsoft Graph channel messages\; n8n Microsoft Teams node or anoth
 er automation tool posting via Graph\nDetails and sources: https://workflo
 wexit.com/shutdowns#teams-office-365-connectors
URL:https://workflowexit.com/shutdowns#teams-office-365-connectors
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:teams-office-365-connectors-connectors-and-incoming-webhooks-stop-worki
 ng@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260522
DTEND;VALUE=DATE:20260523
SUMMARY:Teams Office 365 connectors: connectors and incoming webhooks stop 
 working
DESCRIPTION:Office 365 Connectors in Microsoft Teams (including Incoming We
 bhook)\nVendor: Microsoft\nMay 22\, 2026: connectors and incoming webhooks
  stop working\nWhat stops: Messages sent to Teams through Office 365 Conne
 ctors\, including Incoming Webhook URLs\, are no longer delivered.\nData d
 eleted: No. Past channel messages stay\; only delivery stops\nWhere to mov
 e: Official: Workflows app in Teams (Power Automate) with Workflows webhoo
 ks\; A Teams bot or Microsoft Graph channel messages\; n8n Microsoft Teams
  node or another automation tool posting via Graph\nDetails and sources: h
 ttps://workflowexit.com/shutdowns#teams-office-365-connectors
URL:https://workflowexit.com/shutdowns#teams-office-365-connectors
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:sharepoint-2013-workflows-off-for-new-tenants@workflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20240402
DTEND;VALUE=DATE:20240403
SUMMARY:SharePoint 2013 workflows: off for new tenants
DESCRIPTION:SharePoint 2013 workflows in SharePoint Online (SharePoint Desi
 gner 2013 workflows)\nVendor: Microsoft\nApril 2\, 2024: off for new tenan
 ts\nWhat stops: SharePoint 2013 workflows can no longer be created or run 
 in SharePoint Online.\nData deleted: No. Existing workflows can still be v
 iewed as raw XML files after the turn-off\nWhere to move: Official: Power 
 Automate\; Official: Approvals in Lists and Document Libraries for simple 
 approvals\; Third-party tools that use SharePoint APIs (n8n\, Nintex\, Flo
 wForma)\nDetails and sources: https://workflowexit.com/shutdowns#sharepoin
 t-2013-workflows
URL:https://workflowexit.com/shutdowns#sharepoint-2013-workflows
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:sharepoint-2013-workflows-workflows-stop-running-in-existing-tenants@wo
 rkflowexit.com
DTSTAMP:20261015T000000Z
DTSTART;VALUE=DATE:20260402
DTEND;VALUE=DATE:20260403
SUMMARY:SharePoint 2013 workflows: workflows stop running in existing tenan
 ts
DESCRIPTION:SharePoint 2013 workflows in SharePoint Online (SharePoint Desi
 gner 2013 workflows)\nVendor: Microsoft\nApril 2\, 2026: workflows stop ru
 nning in existing tenants\nWhat stops: SharePoint 2013 workflows can no lo
 nger be created or run in SharePoint Online.\nData deleted: No. Existing w
 orkflows can still be viewed as raw XML files after the turn-off\nWhere to
  move: Official: Power Automate\; Official: Approvals in Lists and Documen
 t Libraries for simple approvals\; Third-party tools that use SharePoint A
 PIs (n8n\, Nintex\, FlowForma)\nDetails and sources: https://workflowexit.
 com/shutdowns#sharepoint-2013-workflows
URL:https://workflowexit.com/shutdowns#sharepoint-2013-workflows
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR