Monitor Jobs

Jobs shows data work such as connector extraction into Lake. Use it to inspect run activity and diagnose missing or outdated data.

Select Data fetching jobs for connector ingestion or SQL jobs for queries that save results to Lake. Use Create job to start the relevant setup.

Create a SQL job to run a query on a schedule.

Bring selected data into Lake

Jobs let you select the data to store in Lake and refresh it on a schedule. You can keep a focused dataset for repeated analysis without importing an entire source.

• Connector data: choose the reports and reporting options supported by the connector. For example, Google Play lets you select report types, App Store Connect supports report families, and advertising connectors provide reporting levels and date windows.
• SQL results: use a read-only SELECT query to choose columns, filter rows and dates, or aggregate the data before saving the result to Lake.

Choose the destination and schedule, and check whether each run appends to or replaces the destination. After the first successful run, inspect the Lake table and its date coverage before using it in an analysis.

Check a run

On Data fetching jobs, expand View activity on the relevant job and inspect its status, progress, and error details. Confirm the destination and reporting period. A connection can remain valid even when a particular extraction fails. Run now, Backfill, and Pause affect the job; opening activity is the read-only inspection step.

After a successful run, inspect the resulting data before relying on an analysis that uses it.

Backfill a historical period

Where supported, use the Job’s backfill action and select the intended date range. Historical availability depends on the provider and report type.

For advertising Jobs, a successful backfill replaces the destination with the requested range. Read the advertising connector guidance before running one.

Investigate failures

Check whether the provider credentials still work, whether the requested data is available, and whether the error reports throttling or missing permissions. Correct the underlying issue before retrying repeatedly.