Review execution configuration
Libraries are resolved automatically. RemoveskipLibs, includeLibs and excludeLibs from Endpoint and Job-template execution options and from equivalent direct execution configuration. A request containing a retired field is rejected even when its value is false, null or an empty array. Do not simply change its value.
These names are still allowed as ordinary business fields in request bodies, event messages or nested business inputs. Change only locations that previously configured library selection.
Before upgrading, identify configurations that intentionally skipped or restricted libraries. Review their source against the automatic behavior and verify the expected business output on a controlled test instance. Keep an export of the original configuration and a tested restore procedure. The upgrade removes the retired options from stored configurations and retained Job execution options, including completed Jobs; a backend downgrade alone does not restore them. Business payloads are preserved.
Coordinate clients and platform
The coordinated version set is:
Use the CLI and editor integration prepared for the 1.8 contract. Old clients can still send removed fields, even if their settings screen shows default values. Re-pull the reviewed configuration after the upgrade and remove obsolete fields from checked-in manifests before the next push.
SDK 4.0.0 targets platform 1.8.0; SDK 3.0.0 remains the matching choice for 1.7.1. Platform and client version numbers are independent. Existing hosted Component revisions keep their recorded SDK until explicitly redeployed; newly created hosted Components use the platform’s supported SDK version. See the SDK guide.
Direct debugging supports
callStrategy: 'caller', 'endpoints' or 'jobs'. The latter two select the instance’s configured execution policy. They do not grant access or accept an arbitrary execution account. Keep view code read-only and verify the effective identity before enabling writes. See Sandbox execution identity.
Verify the workflows you use
- Run a representative Endpoint and Job, including configurations that previously selected libraries. Check their business results, identity and failure behavior.
- Connect an updated terminal runner, choose an assigned Vault profile and verify access independently in each conversation. Complete one human step with Finish & resume, and verify that Skip declines a separate optional step. See browser profiles.
- Open a saved dashboard and a private Assistant widget. Check a form action, the exact Job result, targeted refresh, drill-down and Back. Shared views and fixed snapshots keep controls inactive. See reactive widgets.