Skip to main content
Last updated on

Slack Access and Integration Logs connector limitations

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

This page contains information about known limitations of the managed Slack Access and Integration Logs connector in Lakeflow Connect.

General 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 Lakeflow Spark Declarative Pipelines 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.
  • Column-level selection and deselection are API-only.
  • 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 Lakeflow Spark Declarative Pipelines pipelines for transformations.

Connector-specific limitations​

The limitations in this section apply to the Slack Access and Integration Logs connector.

  • SCD Type 2 isn't supported because Slack access and integration logs are append-only.
  • Slack's retention policy for your plan limits historical data coverage. After Slack no longer returns older entries, the connector can't recover them.
  • The connector supports two prebuilt source tables: access_logs and integration_logs. It doesn't expose other Slack resources.
On this page