Troubleshoot Pipelines and integrations

Use this page to diagnose and resolve issues with BASIC Connections, Data Mapping Templates, Automate, and Pipelines.

Before you troubleshoot

Identify where the issue occurs in the ingestion workflow. This helps you start with the most relevant information instead of changing multiple parts of the configuration at once.

For details about the monitoring views, see Monitor pipeline runs.

Connection issues

Connection test fails or the pipeline cannot reach the source

Possible causes

• The credentials have expired, changed, or been revoked.

• The source-system permissions have changed.

• The configured account, container, bucket, or endpoint is no longer valid.

• API consent is no longer valid.

Resolution

1. Go to Admin > Pipelines > Connections.

2. Open the affected connection.

3. Verify the configured credentials and source details.

4. For API connections that use Platform Credentials, reauthorize the connection through the supported consent flow when required.

5. Select TEST CONNECTION where available.

6. After the connection succeeds, use Run Once on the affected pipeline to validate ingestion.

Power BI connection succeeds, but the pipeline returns no data

What to check

• Confirm that the Power BI application still has the required tenant access.

• Confirm that service principal access remains enabled for the applicable security group.

• Confirm that the correct Power BI data pipeline is active.

• Review View Run History for the most recent execution.

If authorization has changed, update or reauthorize the Power BI connection before rerunning the pipeline.

You cannot delete a connection

Cause

One or more active or inactive pipelines still reference the connection.

Resolution

1. Go to Admin > Pipelines > Pipelines.

2. Identify the pipelines that use the connection.

3. Update those pipelines to use another connection, or delete the pipelines if they are no longer required.

4. Return to Connections and delete the connection after it is no longer referenced.

Data Mapping Template issues

Source fields do not map correctly

Possible cause

The source file structure changed, or the selected Data Mapping Template no longer matches the source fields.

Resolution

1. Compare the source file headers with the fields in the selected Data Mapping Template.

2. Check for renamed, removed, or newly added source columns.

3. Update the template where editing is supported.

4. Run the pipeline again and validate the loaded data.

Cloud Consumption file fails date validation

Possible cause

The Date Format selected for the Cloud Consumption Data Mapping Template does not match the date values in the source file.

Resolution

1. Review the date values in the source file.

2. Confirm that the file uses a consistent date format.

3. Review the Date Format selected for the Cloud Consumption mapping.

4. Select the format that matches the source file.

5. Rerun the pipeline and review the result.

You cannot delete a Data Mapping Template

Cause

An active or inactive pipeline still references the template.

Resolution

1. Identify the pipelines that use the Data Mapping Template.

2. Update the pipelines to use another template, or delete the pipelines if they are no longer required.

3. Delete the Data Mapping Template after no pipelines reference it.

Automate issues

Automation does not run

What to check

1. Confirm that the linked BASIC pipeline still exists.

2. Confirm that the pipeline is active.

3. Verify the configured cloud storage connection.

4. Confirm that the expected source files are in the configured directory.

5. Review the pipeline run history for errors.

You cannot deactivate recurring automation directly from the Automate screen. The linked pipeline controls whether the recurring upload runs.

For the complete setup and folder behavior, see Automate.

You deleted a file from UPLOADED FILES

Deleting a previously uploaded file from the UPLOADED FILES tab does not stop the existing automation. The linked pipeline continues to control future scheduled uploads.

If automation has stopped, check the linked pipeline, connection, source directory, and run history instead of recreating the deleted uploaded file.

Pipeline execution issues

Pipeline did not ingest new data

What to check

1. Confirm that the pipeline is active.

2. Review the configured schedule.

3. For cloud storage pipelines, confirm that new source files exist in the configured directory.

4. Confirm that the files have not already been moved to the Processed or Error folder.

5. Verify the source connection.

6. Review View Run History and Background Processes.

Use Run Once after correcting the configuration when you want to validate the pipeline immediately.

Pipeline does not run at the expected schedule

Resolution

1. Confirm that the pipeline is active.

2. Review the configured frequency and timing.

3. Check Audit Logs for recent configuration or activation changes.

4. For cloud storage ingestion, confirm that the expected source data is available.

5. Use Run Once to verify that the pipeline can execute successfully.

Pipeline is running but does not complete

Resolution

1. Review Background Processes to confirm the current execution state.

2. Review the run details for available errors or long-running steps.

3. Confirm that the source connection remains valid.

4. For file-based pipelines, review the source file size and structure if processing is taking longer than expected.

5. If the run remains unresolved, collect the pipeline name, run time, status, and available error details before escalating the issue.

Files are not detected in the configured cloud storage directory

Resolution

1. Verify that the pipeline's Directory Name matches the source folder.

2. Confirm that the source files are inside that directory.

3. Verify the file naming requirements for that automated data type.

4. Confirm that the storage connection has access to the directory.

5. Check whether the files were already processed or moved to the Error folder.

For recurring file naming and directory guidance, see Automate.

File moves to the Error folder

Possible causes

• The source file failed validation.

• The file structure does not match the selected Data Mapping Template.

• Required fields are missing or invalid.

• The source file format or schema is not accepted for the configured ingestion.

Resolution

1. Review the pipeline run details.

2. Review the source file and Data Mapping Template.

3. Correct the source issue.

4. Place the corrected file in the configured source directory for reprocessing.

API pipeline was created through consent, but data does not appear

Resolution

1. Confirm that the auto-created API pipeline exists and is active.

2. Review its most recent run in View Run History.

3. If the run failed, review the connection authorization and source-system permissions.

4. If the run succeeded, verify the data in its Yarken destination before checking reporting.

5. Refresh the affected cube when the data is loaded but not yet visible in reports or dashboards.

For the supported consent behavior, API data sets, and recommended schedules, see Create BASIC pipelines.

You cannot edit an active pipeline

Cause

Yarken requires you to deactivate the pipeline before editing its configuration.

Resolution

1. Go to Admin > Pipelines > Pipelines.

2. Deactivate the pipeline.

3. Select Edit and update the required settings.

4. Select SAVE.

5. Reactivate the pipeline.

6. Use Run Once when you need to validate the change immediately.

For pipeline lifecycle actions, see Manage BASIC pipelines.

Duplicate data appears after ingestion

What to check

• Confirm that the source folder contains only the intended new files.

• Check whether overlapping source periods were provided in multiple files.

• Review run history to identify which source files or runs affected the period.

• For Expenses ingestion, review whether the workflow should replace existing data for the target period.

Do not move files from the Processed folder back into the monitored source directory for routine reprocessing.

Post-ingestion issues

Pipeline succeeds, but expected data is missing in Yarken

Resolution

1. Review View Run History and confirm that Yarken processed the expected source data.

2. For file-based ingestion, verify the selected Data Mapping Template.

3. Open the Yarken feature associated with the destination data type.

4. Verify the applicable entity, year, month, and other filters.

5. If the expected records are still missing, review the source file and run details before escalating the issue.

Data is loaded, but it is missing from reports or dashboards

Resolution

1. Confirm that the expected records are available in the destination feature.

2. Open Cube Refresh and review the affected cube.

3. Run a manual cube refresh when you need the latest data immediately.

4. Review the report or dashboard again after the refresh completes.

For current refresh guidance, see Cube Refresh.

When to escalate an issue

If the issue remains after you complete the applicable checks, capture the information needed to investigate the run:

• Pipeline name.

• Connection or source type.

• Execution date and time.

• Run status.

• Available error message or run details.

• Source file name and affected period for file-based ingestion.

• Whether the issue occurs with Run Once, scheduled execution, or both.

Related content

• Pipelines and integrations

• Connections

• Data Mapping Templates

• Automate

• Pipelines

• Create BASIC pipelines

• Manage BASIC pipelines

• Monitor pipeline runs

• Troubleshoot Advanced Integrations