Arcade 1.11.3Preview

A gateway created without an explicit tool-discovery setting now defaults to on when the project has tool recommendation available, instead of always defaulting to off. An explicit value in the create request still wins, and gateways created before this release keep whatever they already had. Installs that don't run discovery, or whose project hasn't turned tool recommendation on, see no change. A flip to the project's tool-recommendation setting can take a few minutes to reach new gateways, because the default is read through a short-lived cache.

Many toolkit parameters accepted null and replaced it with one fixed value before running, even though the parameter's own documentation promised that default — so a caller that sent null explicitly could get different behavior than a caller that left the field out entirely. For example, a request that sent null for a sort direction returned the oldest comments first, instead of the newest-first order the tool's own description promised. Affected parameters across many toolkits (including GitHub, Google Maps, Google Contacts, Google Drive, Google Hotels, HubSpot, Jira, Outlook Mail, Reddit, Salesforce, Slack, Spotify, Zendesk and Daytona, among others) now reject null and require the real value instead. Review any integration that explicitly sends null for an optional toolkit parameter against the current tool schemas.