Execution Logs

LiteLambda captures all standard output (stdout) and standard error (stderr) generated by your Python script during execution. This makes debugging scheduled jobs as easy as debugging local scripts.

Viewing Logs

To view logs, navigate to the Dashboard, click on your Cron Job, and select the Logs tab. This view shows a history of all past executions, sorted by the most recent.

Each execution record shows:

• Status: Success, Error, or Timeout.
• Duration: Exactly how long the script took to run (in milliseconds).
• Trigger: Whether the job was triggered automatically by the "Schedule" or clicked "Manually".

What gets logged?

Any use of the standard Python print() function will be captured as an INFO-level log line. If an unhandled exception occurs, the full Python traceback is automatically captured as an ERROR-level log line.

def handler(event, context):
    print("This will appear in the logs as an INFO message.")
    
    # This will generate an ERROR traceback in the logs
    x = 1 / 0 
    
    return {"status": "never reached"}

The Return Dictionary

In addition to printed output, the dictionary returned by your handler function is saved and displayed prominently at the top of the execution log details. This is useful for returning summary metrics (e.g., {"rows_processed": 142}).

Data Retention

Execution logs are currently retained indefinitely for all users. However, in the future, log retention may be limited based on your subscription tier (e.g., 7 days for Free tier, 90 days for Pro tier).

Automatic Pausing

If a cron job fails (returns an ERROR status or TIMEOUTs) for 10 consecutive executions, LiteLambda will automatically pause the job to prevent infinite failure loops and wasted credits. You will receive an email notification when this happens.