Before you start
A Session reuses a published Mapping in an execution context. It does not redefine the algorithm. Prepare an accepted revision, authorized location and compatible capacity. Keep editing, publishing and execution permissions separate. Browser-local files do not automatically appear in a worker filesystem.
Choose a laboratory environment and destination before testing writes. Classifying the environment as Production does not grant permission or publish the artifact.
Procedure
- Create the Session and choose the published Mapping. Check its identifier and revision, not only its name.
- Review the environment and worker policy. Keep inherited selection unless an explicit assignment is needed; any choice must satisfy capabilities and permissions.
- Complete connections and input/output bindings. Use paths accessible by the selected worker and an exclusive test destination.
- Configure declared parameters with correct types. Task overrides belong to the Workflow, not Session layers.
- Review timeout, retries and recovery. Save the draft and publish the accepted revision before consuming it in a Workflow.
Synthetic example
A Mapping reads CSV name,amount and retains both columns. Create two Sessions referencing the same Mapping: one for Test and another for Stage. Use equivalent inputs and different outputs. Path differences belong in bindings; there is no need to duplicate the algorithm merely to change a file.
Verify the result
Reopen the Session and verify Mapping reference, revision, environment, worker policy and bindings. For parameters, inspect the source of each resolved value. Create a laboratory Workflow for each context and compare output schema and data. Successful saving does not establish that connections or files will be accessible during execution.
When a Mapping changes, review the dependency notice and deliberately accept the new revision. Then check Workflows consuming that Session.
Troubleshooting
For a missing file, correct its binding and check worker permissions. For unavailable capacity, distinguish worker state, slots, requirements and tenant policies. Fix invalid JSON without discarding other draft settings. A checkpoint only helps when usable state exists; it does not automatically reverse external writes. Before repeating a load, determine whether the destination supports retries without duplicates. Record which published revision each test consumes.
Runtime: profile, filenames and variables
In Runtime select Execution profile and compare input, memory, disk and timeout limits with worker capacity. An automatically selected profile can allow fewer bytes than your file; free VM disk does not increase that limit or isolated executor temporary memory.
Available runtime variables shows the name, meaning, Example preview and Last resolved value. The example helps prepare configuration; the resolved value belongs to the identified run and date. Sensitive values are masked. When no compatible execution is available, an example does not substitute for an actual value.
For output names use Target filename timestamp and Target filename template. %RUN_TIMESTAMP% resolves when the attempt starts. Enabled activates it for that Session; Disabled disables it; Inherit follows the global preference. Writing the token into a template while inherited mode is disabled does not activate substitution. Filename preview · example illustrates a filename rather than proving a run's actual output. Save and publish so consumers can adopt your change.
General: choose location before Mapping
After Name, complete Domain → Folder → Mapping, followed by Environment and Status. Available mappings are filtered by Domain and sharing permissions and load when the form opens, without reselecting Domain. Folder organizes the Session and does not require its Mapping to be in the same folder. After changing location, review the choices and keep a valid reference before saving.
Optional TRACE
In Sessions → Runtime, TRACE offers Inherit from Workflow, Enabled or Disabled. Inherit from Workflow follows the invoking Workflow; a directly executed Session without a Workflow resolves inheritance as disabled. Enabled and Disabled override inheritance for that Session. Inherit from Workflow is the default, and new Workflows have TRACE disabled.
This setting controls TRACE detail generation for new attempts; it neither removes historical evidence nor hides INFO, WARNING or ERROR. Save, publish and update Workflow dependency versions when needed to execute the accepted setting.
Environment context
Before using this module, confirm Tenant, Domain and Environment in the user menu. The initial environment is Development. Module, Domain and environment capabilities apply together; Production is read only without explicit authorization. Switching the selector does not move artifacts or publish or execute their data. See environments and recovery and environment promotion.
Unassigned worker
Before running again, select compatible authorized capacity and review the environment pool. Unassigned does not silently choose another worker. You can provision a new VM and assign it explicitly. Permissions, resource ownership, the protected base server and pending operations remain checked; removal does not bypass these protections.
List toolbar and environment scope
In the Sessions list, action buttons use icons with help and accessible names and align with Search and filters. Identify them by hovering or moving focus with Tab. The Environment filter is removed from this list: it uses the Tenant, Domain and Environment context selected in the user menu and visible in the bottom operational status bar. Runtime and the other filters remain available. This list change does not remove the Session Runtime configuration or its worker requirements.