Skip to content
Lyft Data Docs (Beta)

Running A Job

Make sure the server is licensed and at least one worker is online; otherwise deployment will fail.

Quick checklist

  • Server licensed and reachable at http://localhost:3000
  • Worker shows Online in the dashboard and via /api/workers
  • Job saved with a meaningful name before staging
  • Run & Trace validates the expected event flow
  1. Open the Jobs area from the main navigation and click New job. The quick setup wizard appears.
  2. Choose Skip quick setup to open the raw editor. The canvas starts empty until you add an input, actions, and an output.

visual editor

Name and save the job

The canvas starts with the placeholder name new-job (unsaved). Rename it before you save—the supported rename flow later is to clone the job under a new name and redeploy. Pick a meaningful name, click OK, then use the Save button in the top-right corner.

first job

Test with Run & Trace

  • Click Run to execute the job in a transient sandbox. The output pane shows the events that flow through the pipeline.
  • Use Run & Trace after the first run to see how each action transforms the event.
  • Transient runs stop automatically based on the limits shown in the dialog so you cannot accidentally consume unbounded data.

To adjust the input, choose Configure inside the Echo block. Even this simple input highlights patterns you will see across all connectors:

  • Trigger controls the schedule. Echo defaults to a single run; other inputs support intervals or cron expressions.
  • JSON toggles whether the incoming payload is parsed as JSON or treated as raw text.
  • Ignore linebreaks decides whether each line becomes a separate event or the whole payload is treated as one record.

echo options

When JSON parsing is disabled, the event appears as a JSON object with _raw holding the original string. For example hitting Run & Trace with two lines entered produces:

{"_raw": "hello"}
{"_raw": "there"}

Turn on Ignore linebreaks to collect the payload into a single event:

{
  "_raw": "hello\nthere"
}

Schedule and deploy

Ready to run the job continuously?

  1. Open the Trigger section on the input and choose an interval (for example 5m) or a cron expression.
  2. Click Stage to create a deployable version of the job. Staging validates the configuration and freezes the definition for deployment.
  3. From the Deployments tab, select the worker you prepared in Getting started and press Deploy.
  4. Watch the live run history or use Run & Trace again to confirm the deployed worker receives events.

Use Cancel run whenever you need to stop a long-running transient execution.

Where to go next