Skip to main content
Last updated on

Workday Activity Logging connector limitations

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Workday Activity Logging from the Previews page. See Manage Databricks previews.

The managed Workday Activity Logging connector ingests only the activity_logging table and can initially fetch up to the previous 30 days of events.

General software as a service (SaaS) connector limitations​

The limitations in this section apply to all SaaS connectors in Lakeflow Connect.

  • When you run a scheduled pipeline, alerts don't trigger immediately. Instead, they trigger when the next update runs.
  • When a source table is deleted, the destination table is not automatically deleted. You must delete the destination table manually. This behavior is not consistent with Spark Declarative Pipelines on Lakeflow behavior.
  • During source maintenance periods, Databricks might not be able to access your data.
  • If a source table name conflicts with an existing destination table name, the pipeline update fails.
  • Multi-destination pipeline support is API-only.
  • You can optionally rename a table that you ingest. If you rename a table in your pipeline, it becomes an API-only pipeline, and you can no longer edit the pipeline in the UI.
  • If you select a column after a pipeline has already started, the connector does not automatically backfill data for the new column. To ingest historical data, manually run a full refresh on the table.
  • Databricks can't ingest two or more tables with the same name in the same pipeline, even if they come from different source schemas.
  • The source system assumes that the cursor columns are monotonically increasing.
  • The connector ingests raw data without transformations. Use downstream Spark Declarative Pipelines on Lakeflow pipelines for transformations.

Connector-specific limitations​

The limitations in this section apply to the Workday Activity Logging connector.

  • The connector ingests a single table, activity_logging. It doesn't ingest other Workday API resources.
  • The initial fetch includes up to the previous 30 days of activity log events. Events older than this window aren't available to the connector.
  • The connector doesn't support SCD type 2 because activity log records are append-only.
  • The connector doesn't support UI-based pipeline authoring, API-based row filtering, or automated schema evolution.
On this page