Introduction
This guide explains two common transform states in Kleene that can cause confusion: transforms showing as Skipped and transforms running off-schedule. Use the steps below to identify the cause and restore the expected run order.
Skipped transforms
A transform marked as Skipped is usually not the root problem. In a chain of transforms, if one transform fails, every downstream transform is not executed and is given the Skipped status.
To resolve this, find the first failing transform in the chain and fix that issue. Once the upstream failure is resolved, the skipped transforms should run as expected.
Off-schedule transforms
A transform running off-schedule is usually caused by conflicting schedule settings. If a transform has upstream dependencies and is also assigned its own schedule, those settings can conflict.
Transforms with dependencies should not be separately scheduled, because the upstream dependencies should trigger the run instead.
How to fix a transform that is running off-schedule
- Open the transform settings.
- Toggle the manual tables off.
- Save the transform.
- Reopen the transform and confirm that the input tables are now dependency-based.
- Reload the page to refresh the view and confirm that the transforms are aligned.
Summary
If a transform is Skipped, look for the first failing transform earlier in the chain. If a transform is running off-schedule, check for conflicting schedule settings and remove the separate schedule so dependency-based triggering can take over.
Next steps
If the issue continues after following these steps, review the transform chain and scheduling configuration in Kleene or contact support with details of the affected transforms and their status.