Latest Releases
Manual Error Handling Improvements
You now have more control over errors when choosing manual error handling. With this change, Tray will follow the failure paths for all errors without any automatic retries and backoffs. This now allows you to reference the error message allowing you to action errors in the manual handling path.
Your workflows will continue to use the existing error behaviours unless you explicitly disable it in the workflow settings. This gives you full control over when and where to adopt the new behaviours, without any risk of disruption to your current workflows.
For full information, including on how to enable this please visit our What is an Error documentation.
Orderful v1.1
A new minor Orderful connector version has been released. It contains the following updates:
Operation Updates:
Create transaction name input is now ddl
Vector Tables updated
The Vector Tables connector has been updated.
Operation bugs:
Fixed some minor bugs
Create and Retrieve Namespace CDK Commands
You can now create and retrieve namespaces for your organisation using the following new commands introduced to the tray CDK. You no longer need to contact support desk before deploying your first CDK connector deployment to the platform.
To create a new namespace for your organisation:
$ tray-cdk namespace create ORGID NAMESPACE [--us] [--eu] [--ap]
To retrieve a namespace from your organisation:
$ tray-cdk namespace get ORGID [--us] [--eu] [--ap]
Where ORGID is the unique identifier of your organisation, which can be found in the tray app URL, for example https://app.tray.io/workspaces/ORGID
When creating a namespace we recommend:
Associating with your company’s legal entity or brand name
Choose a shorter name over a longer one
Hyphens are supported, numbers and other symbols are not supported
For example
enter-company-name
New Variables in Alerting Workflows
We've expanded the available variables for alerting workflows. In the alerting trigger, you can now access:
workspace_id
workspace_name
project_id
of the failing workflow. This makes it easier to identify where errors originate and improve error-handling processes.
SDLC: Improved Workflow Cleanup During Project Import
We've updated how workflows are handled during project imports to ensure better consistency and prevent unintended workflow execution. When importing a project that has had workflows removed, those workflows will now be deleted in the destination project rather than being detached and preserved as standalone workflows.
For example, when importing a project from development to production, any workflows deleted in development will now be automatically removed from the production project, maintaining perfect synchronization between environments.
This change helps prevent potential confusion and security risks from orphaned workflows that previously would have continued running outside project scope.
Instantly Test Workflows with Mock Data
You can now easily test workflows that start with non-manual triggers - no more complicated workarounds.
Simply provide mock trigger output data and run the workflow immediately, just as if the real event had occurred.
To make this even easier, we’ve added Raw JSON input, allowing you to define test data freely - no UI restrictions. Use the Basic editor for structured input or switch to Raw JSON for full control.
This feature is currently available for a subset of non-manual triggers:
Alert
API Operation
Callable
Email
Form
Schedule
Webhook
Optional Strict Mode for Schema Validation
We've introduced the ability to disable Strict Mode in API Operation triggers, offering more flexibility in handling JSON payloads. This enhancement allows fields not defined in the schema to flow through to your workflow instead of being filtered out.
