Transform Logs and Slowness Behaviour

Introduction

When a transform in Kleene seems slow or does not appear to be running - the best place to start is the logs. The log messages show whether the transform is waiting in the queue or actively executing in the data warehouse, which helps you understand where the delay is happening.

What the log messages mean

Kleene uses a few key log messages to show the progress of a transform. Each message tells you something different about where the transform is in the process.

How to tell whether a transform is actually running

An Execution-started log does not mean the transform has begun running. It only means the transform has entered the queue. The transform may still be waiting if other transforms are ahead of it or if it depends on an upstream transform that has not finished yet.

Once you see a Starting-task log, the transform is actively running in the data warehouse. To measure the real run time, check the time between the Starting-task and Completed-task logs in the App log section.

Why transforms can appear slow

Slow run times are often caused by queue congestion rather than by the transform itself. If long-running transforms are scheduled too frequently, they can clog the queue and delay other transforms behind them.

What to do next

If a transform appears slow, check the logs first to confirm whether it is still queued or is already running. If the run time is genuinely excessive, contact Kleene support so they can investigate ways to speed up the transform.

Summary

Execution-started means the transform is queued, Starting-task means it is running, and Completed-task means it has finished. Use these logs to distinguish queue delays from actual execution time and to decide whether further investigation is needed.