Highlights
- Collect Event, Schedule, manual and low-code triggers with Job Template Batch or Debounce and process them in order with
api.walkTriggers(). - Inspect a Job’s triggers and retry history, find initiating accounts, and open a complete JSON cell without loading every payload into a list.
- Compress uploads and database exports, and read supported gzip files through native Storage tools.
- Share restricted Secrets with selected workloads and embed an external frontend in a dashboard.
In detail
Collect executions with explicit Job inputs
Configure Batch or Debounce on the Job Template to collect Event, Schedule, manual and programmatic triggers into one Job. Release on size, maximum wait or quiet period; every accepted trigger remains available in order. Job Template values stay intemplateInputs; each trigger carries its own input, message and source. Authorized callers and Assistant conversations can join one group; the Job uses its configured shared execution account and each trigger retains its own initiator and origin. Manual Run has separate editors for template inputs and explicit triggers. Use api.walkTriggers() for the same native code across small and large batches. New Event messages have a 1 MB limit; pass larger data through Storage references. See Event delivery and Jobs.
Admit direct Jobs atomically
Useapi.triggerJobs to admit up to 100 direct Jobs together, with a stable idempotency key and ordered Job IDs. Repeating the same ordered request recovers its first receipt. Producer loops have bounded host admission. Template execution mode decides whether accepted items create separate Jobs or join a group; ordered Job IDs can repeat. SDK transport separates its packing target from the hard frame limit, preserving full-size Event messages. See atomic Job batches.
Inspect triggers and full JSON values
Open Triggers in Job details to page through occurrences, inspect a selected payload and follow its source. Data grids show JSON and metadata values that fit the column. Click any value or the remaining-item count to open the entire cell. Lists use bounded previews; selecting a cell loads its full value. Explicit JSON columns in low-code queries and exports continue returning complete values. See Databases and Job operations.Trace retries and initiating sources
Job History shows each attempt’s historical position, including manual retries, and opens the attempt list after retrying a Job with automatic retry disabled. Compact Status and Result columns share icons with their filters. Trigger replaces the separate Requested by column: manual Request/Retry show the initiating user, and low-code Execution links to the source Job. Search accounts by name or email under their existing access permissions. Audit fields remain separate in the API. See Job History.Compress uploads and database exports
Enable gzip on an upload or CSV, TSV, NDJSON or XLSX export. Supported native readers can decode gzip files; downloads preserve archive bytes. Choose Compress or Unpack in Storage file details, or usestorage.compress and storage.unpack. The source is preserved. For repeated reads, prepare indexed access immediately or in the background. See Storage uploads and Storage.
Share Secrets and embed external applications
New instance Secrets default to Restricted. Grant access to selected users, service accounts or groups; existing Secrets retain their prior policy until explicitly changed. Add an Iframe dashboard widget with a chosen isolation profile for an external HTTPS application. See Secret access and dashboard embedding.Author typed dashboards
Use shared DashboardElementInterface and DashboardRowInterface declarations, WidgetContextInterface and matching JavaScript/TypeScript examples in Monaco and VS Code. Editor completion and diagnostics describe the existing widget runtime without changing its output format. See dashboard authoring.Upgrade Job callers and clients together
Native low-code and SDK 4.1.0 useapi.triggerJob(name, trigger, options?). SDK 4.1.0 intentionally changes the earlier flat-input contract: move run values into trigger.input and read the resulting EXECUTION trigger. Event and Schedule input no longer overlays template values; inputMode is retired. Previously queued Jobs and published SDK 4.0.0 retain their recorded contract. Review both callers and Job Components before upgrading. See the 1.9 upgrade guide.