Breadcrumbs

Troubleshooting Common Issues in Yarken Advanced Integrations

Overview

This page describes common issues that may occur when configuring or running advanced integrations in Yarken and provides recommendations to help you resolve them.

Most integration issues are related to authentication, connection configuration, automation recipe execution, or data processing.

If you're experiencing problems with a specific integration, start by reviewing the connection status and recipe execution history before investigating provider-specific configuration.

Troubleshooting workflow

Use the following workflow to identify and resolve common integration issues.

Integration issue
        │
        ▼
Verify the connection status
        │
        ▼
Review the automation recipe
        │
        ▼
Check the execution history
        │
        ▼
Review authentication and permissions
        │
        ▼
Validate imported data
        │
        ▼
Retry the integration

Following this process helps isolate whether the issue is related to authentication, configuration, or data processing.

Connection issues

Connection remains Access Requested

Possible cause

The connection has not been authorized.

Resolution

  • Open the connection.

  • Complete the required authentication.

  • Save the configuration.

  • Verify that the status changes to Connected.

Connection test fails

Possible causes

  • Incorrect credentials.

  • Invalid endpoint or URL.

  • Network connectivity issues.

  • Expired authentication token.

Resolution

  • Verify the authentication details.

  • Confirm the endpoint URL.

  • Test the connection again.

  • Reauthorize the connection if required.

Connection status changes to Error

Possible causes

  • Authentication credentials have expired.

  • The external system is unavailable.

  • Required permissions have changed.

Resolution

  • Update the authentication credentials.

  • Test the connection.

  • Confirm that the required permissions are still assigned.

Automation recipe issues

Recipe will not start

Possible causes

  • One or more required connections are unavailable.

  • Required configuration is incomplete.

Resolution

  • Verify that all required connections display Connected.

  • Review the recipe configuration.

  • Start the recipe again.

Recipe stops unexpectedly

Possible causes

  • A runtime error occurred.

  • Authentication failed during execution.

  • The external system rejected the request.

Resolution

  • Review the recipe execution history.

  • Resolve the reported error.

  • Restart the recipe after correcting the issue.

Scheduled recipe does not run

Possible causes

  • The recipe is stopped.

  • The schedule is incorrect.

  • The trigger conditions have not been met.

Resolution

  • Confirm that the recipe is running.

  • Verify the configured schedule.

  • Review the trigger configuration.

File upload issues

Files are not detected

Possible causes

  • The monitored folder is incorrect.

  • The file naming pattern does not match.

  • The recipe trigger has not been activated.

Resolution

  • Verify the configured folder or bucket.

  • Confirm the expected file naming convention.

  • Upload a test file.

File upload fails

Possible causes

  • Invalid authentication.

  • The destination connection is unavailable.

  • The upload request was rejected.

Resolution

  • Verify the cloud storage connection.

  • Verify the Yarken connection.

  • Retry the upload.

Pipeline does not process the uploaded file

Possible causes

  • The upload completed successfully, but the destination pipeline is unavailable.

  • The Data Mapping Template is incorrect.

  • The uploaded file does not match the expected format.

Resolution

  • Verify the pipeline configuration.

  • Review the selected Data Mapping Template.

  • Confirm that the uploaded file matches the expected format.

Data validation issues

Imported data is missing

Possible causes

  • The automation recipe completed before the source data was available.

  • Required records were not returned by the external system.

Resolution

  • Verify that data exists in the source application.

  • Run the recipe again.

Imported data is incorrect

Possible causes

  • Incorrect mapping configuration.

  • Invalid source data.

  • Unexpected changes in the source system.

Resolution

  • Review the Data Mapping Template.

  • Validate the source data.

  • Process the file again after correcting the issue.

Imported data is not visible in reports

Possible causes

  • The pipeline has not completed.

  • The affected cube has not been refreshed.

Resolution

  • Verify that the pipeline completed successfully.

  • Refresh the affected cube if required.

  • Validate the data again.

AWS Trusted Advisor issues

Issue

Resolution

No recommendations are imported

Verify that the AWS account has Business Support (or higher) and that the required IAM permissions have been configured.

Authentication fails

Review the AWS connection configuration and reauthorize the connection.

Recipe completes but no recommendations are returned

Confirm that recommendations exist in AWS Trusted Advisor for the selected account.

Cloud storage issues

Issue

Resolution

Files are not retrieved

Verify the monitored folder, bucket, or container configuration.

Authentication fails

Review the cloud storage connection and update the credentials if required.

Incorrect file is processed

Verify the configured file naming pattern and source location.

Related content