# Pascal Workflows

Source: https://www.trypascal.io/platform/workflows

Keep work moving across every handoff.

Coordinate people, agents, and systems through repeatable processes. Keep progress intact through long waits, human reviews, and failed steps.

## Capabilities

### Define the sequence

Connect the steps, inputs, and conditions that make up a repeatable operation.

### Coordinate across systems

Compose approved business functions and connected tools. Keep each step tied to its input and expected result.

### Wait for the right moment

Pause for a person, signal, or scheduled point without losing the work already completed.

### Keep progress visible

Follow a run through its steps, waiting states, failures, and completed results.

### Recover with context

Inspect what happened before retrying or repairing a failed step. Preserve completed work and uncertain outcomes.

### Review the version

Keep a run connected to the workflow definition it uses. Review changes before applying a new version.

## Connected context

Combine agent recommendations and Forge functions in a process connected to Compass cases. Start deployed Workflows from schedules, webhooks, or supported platform events through Automations.

- Revisioned drafts and immutable releases
- Deployments and runs
- Steps, waits, outputs, and human tasks

## Controls and permissions

Review and publish a version before deploying it. Each run records the steps and results it confirms, including work still waiting or unresolved. Requesting a change to a run does not mean that change has finished.

## Example

A recovery decision creates follow-up work across carriers and customs. The Workflow connects those steps and retains their outputs. In this example, all three steps have completed, but completion updates are still finalizing. The team can inspect the recorded work while keeping that unresolved status and the three lithium holds visible.

## Workflow

### Understand the defined process

- The Workflow connects confirmed tender writebacks to carrier and customs follow-ups. Three hazardous loads remain outside the approved shipment scope.

### Open the recorded run

- The run history shows a seven-second execution. Open it to inspect the steps, outputs, and any completion work still pending.

### Check the result and remaining work

- Three steps are complete. The final output records 14 approved shipments and three held loads. Completion updates are still finalizing, so the run remains unconfirmed until those updates arrive.

## Next steps

Choose a workflow that crosses teams or systems. Map its steps, approvals, waiting periods, and what should happen when a step fails.

- [Contact sales](https://www.trypascal.io/contact)
- [Logistics](https://www.trypascal.io/solutions/logistics)