Breadcrumbs

Troubleshoot Advanced Integrations

Use this page to identify and resolve common issues with Advanced Connections and Advanced pipelines in Yarken.

Start with the connection status, then review the Advanced pipeline and its run history. If the issue is specific to a provider, use the relevant integration guide for provider credentials, permissions, source data, and limitations.

Troubleshooting workflow

Use the following sequence to isolate the issue:

  1. Check the Advanced Connection — Confirm that the required connection shows Connected.

  2. Check the Advanced pipeline — Confirm that the expected pipeline is available and review whether recurring execution is active when required.

  3. Review the latest run — Check Last run, Last status, Succeeded, and Failed.

  4. Review run history — Open the failed or unexpected run and review its Error and job details.

  5. Verify provider access — Check the provider credential, permissions, account settings, and source data required by the integration.

  6. Run the pipeline again — After correcting the issue, use Run to validate the integration.

  7. Validate the destination data — Confirm that the expected data is available in the Yarken destination used by the integration.

Advanced Connection issues

Connection remains Access requested

Possible causes

  • The provider authorization has not been completed.

  • A required connection field is missing or incorrect.

  • The credential does not have the access required by the integration.

What to do

  1. Go to Admin > Pipelines > Connections > ADVANCED.

  2. Open the affected connection.

  3. Verify the required provider-specific fields.

  4. Confirm that the credential and provider permissions match the relevant integration guide.

  5. Select Connect.

  6. Confirm that the status changes to Connected.

A previously connected integration stops working

Possible causes

  • The provider credential expired, was rotated, or was revoked.

  • The provider permissions or account settings changed.

  • The provider is temporarily unavailable.

What to do

  • Review the provider credential and access settings.

  • Update or reconnect the Advanced Connection when required.

  • Confirm that the connection returns to Connected.

  • Run the affected Advanced pipeline manually to validate the connection.

For connection procedures, see Authorize Advanced Connections.

Advanced pipeline issues

The expected Advanced pipeline is not available

Possible cause

The Advanced Integration has not been enabled or deployed for your environment.

What to do

Confirm that the integration has been enabled for your environment. Advanced Integrations are deployed by Yarken and are not created by customers from the Advanced pipeline page.

The pipeline does not run automatically

Possible causes

  • The pipeline is inactive.

  • The integration is not configured for recurring execution.

What to do

  • Go to Admin > Pipelines > Pipelines > ADVANCED.

  • Locate the affected pipeline.

  • Confirm its active state.

  • If recurring execution should be enabled, activate the pipeline.

You can use Run to start an Advanced pipeline manually even when recurring execution is inactive.

The latest pipeline run failed

What to do

  1. Open the affected Advanced pipeline.

  2. Review Last status and the Failed count.

  3. Open the failed run from the run history.

  4. Review the displayed Error and job details.

  5. Confirm that the required Advanced Connection still shows Connected.

  6. Check the provider-specific guide for required credentials, permissions, and source requirements.

  7. After correcting the issue, select Run to test the integration again.

The pipeline succeeds but expected data is missing

Possible causes

  • The source provider returned no supported data for the collection period.

  • The source file or source data was not available when the integration ran.

  • The integration is configured for a different source account, resource, bucket, or scope.

  • The data loaded successfully but has not yet been validated in the correct Yarken destination.

What to do

  • Confirm that the expected data exists in the provider.

  • Review the provider-specific integration guide for data availability and source requirements.

  • Run the pipeline again after the source data is available.

  • Validate the data in the destination used by the integration.

For common pipeline controls and run-history fields, see Manage Advanced pipelines.

Cloud storage ingestion issues

The expected file is not ingested

What to check

  • The file is in the configured bucket, container, or source location.

  • The file follows the expected naming and source-format requirements.

  • The cloud storage Advanced Connection shows Connected.

  • The Advanced pipeline ran after the file became available.

Data is loaded incorrectly

What to do

  • Confirm that the source file matches the format agreed for the integration.

  • Do not edit the Data Mapping Template used by the Advanced Integration.

  • Contact Yarken if the deployed mapping needs to be reviewed or updated.

For provider-specific cloud storage fields and ingestion guidance, see Cloud storage Advanced Integrations.

Data validation issues

Data is available in the destination but not in reporting

What to do

  • Confirm that the expected records are present in the integration's destination.

  • Refresh the affected cube when applicable and when an immediate reporting refresh is required for that data.

  • Recheck the report or dashboard after the refresh completes.

Imported values do not match the source

What to do

  • Compare a representative source record with the corresponding Yarken record.

  • Confirm that the source data falls within the supported fields and collection behavior documented for the integration.

  • Review any provider-specific limitations or data interpretation notes.

  • If the source is correct but the Yarken result is not, capture the affected run and contact Yarken for further investigation.

Information to collect before contacting Yarken

If you need additional support, collect the following information where available:

  • The integration and provider name.

  • The Advanced Connection status.

  • The Advanced pipeline name.

  • The date and time of the affected run.

  • The run Status and displayed Error.

  • Whether the issue affects all runs or a specific source account, resource, or file.

  • The Yarken destination where you expected the data to appear.

Do not include API keys, access tokens, client secrets, private keys, passwords, or other credentials in screenshots or support messages.

Provider-specific troubleshooting

Use the relevant integration guide when the issue depends on provider credentials, permissions, source behavior, or data limitations.

Related content