The WORKFLOW_RUN Table Is Missing From the Destination

Issue

The WORKFLOW_RUN table can be included in the connection schema. However, after a historical sync completes, the table isn't created in the destination.

Environment

Connector: GitHub

Resolution

To resolve this issue:

1. Ensure the GitHub token or app installation can access the relevant repositories and read GitHub Actions workflow runs. For private repositories, grant the repo scope.
2. In Fivetran, go to your GitHub connection page.
3. Select the Settings tab.
4. Click Edit connection.
5. Click Re-Authorize Connection and complete the authorization process.
6. Click Save & Test.
7. In the top right, click Sync.

After GitHub returns workflow run records, we create the WORKFLOW_RUN table in the destination.

For more information, see see Configure GitHub for authentication and the GitHub API documentation on workflow runs.

Cause

This issue occurs when the GitHub authorization lacks permission to access workflow run data and we don't receive any relevant records. We don't create empty tables for GitHub connections, so we don't create the WORKFLOW_RUN table in your destination when this happens. For more information, see Syncing empty tables and columns.