Manage BASIC pipelines

Use this guide to manage existing BASIC pipelines after you create them. You can update the configuration, run a pipeline on demand, control scheduled execution, and remove pipelines you no longer need.

Go to Admin > Pipelines > Pipelines, then select the BASIC tab.

This page applies to BASIC pipelines. For pipelines delivered through Advanced Integrations, use the applicable Advanced integrations guide.

What you can do

After you create a BASIC pipeline, you can:

Edit supported pipeline settings.
Run the pipeline immediately with Run Once.
Activate scheduled ingestion.
Deactivate scheduled ingestion without deleting the pipeline.
Review pipeline execution history.
Delete pipelines that are no longer required.

Before you make changes

Confirm that you selected the correct pipeline.
Review the current connection, source, mapping, and schedule before you edit the configuration.
Confirm whether the pipeline was created through Automate. Changes to that pipeline also affect the automated upload workflow.
Test updated source credentials from Connections before you rely on the next scheduled run.

Changes to a pipeline affect future scheduled and manual runs. Review the configuration before you save an update.

Edit a pipeline

Edit a pipeline when the ingestion requirements change.

Depending on the pipeline type, you can update:

The schedule frequency.
The Data Mapping Template for cloud storage pipelines.
The selected API data for API pipelines.
The pipeline name or description.
Other supported source details shown in the pipeline configuration.

Step 1: Open the pipeline

Go to Admin > Pipelines > Pipelines.
Select the BASIC tab.
Find the pipeline you want to update.
Select the Edit icon.

Step 2: Update the configuration

Change the required pipeline settings.

If you change the Data Mapping Template, confirm that it matches the structure and destination of future source files.

Step 3: Save and validate the change

Review the updated settings.
Select SAVE.
Use Run Once to validate the new configuration when an immediate test is required.
Review the next run result.

The updated configuration applies to future scheduled and manual runs.

Run a pipeline on demand

Use Run Once to start an immediate pipeline execution without changing its recurring schedule.

Run Once is useful when you want to:

Test a new pipeline configuration.
Validate an updated connection or mapping.
Process newly available source data without waiting for the next scheduled run.
Refresh the ingested data before the next scheduled execution.

Run the pipeline

Find the active pipeline.
Select Run Once.
Select OK on the confirmation message.

Yarken starts retrieving data from the configured source.

Run Once does not change the existing schedule. The pipeline continues to run at its configured recurring frequency.

A BASIC pipeline must be active before scheduled or on-demand execution is available.

Use View Run History to confirm the execution result. For detailed monitoring guidance, see Monitor pipeline runs.

Activate a pipeline

New BASIC pipelines are inactive by default. Activate a pipeline when you are ready for scheduled and on-demand execution.

Find the inactive pipeline.
Turn on the activation toggle.
Select OK on the confirmation message.

The pipeline is active. Yarken can now run it according to the configured schedule or when you use Run Once.

Deactivate a pipeline

Deactivate a pipeline when you want to pause ingestion without deleting its configuration.

Find the active pipeline.
Turn off the activation toggle.
Select OK on the confirmation message.

After deactivation, the pipeline does not run on its scheduled frequency.

Deactivation keeps the pipeline configuration. Reactivate the pipeline when you want recurring ingestion to resume.

If the pipeline was created through Automate

Deactivating the linked pipeline also stops the recurring Automate workflow for that file type.

The automation remains configured, but it does not run while the pipeline is inactive.

See Automate for the complete workflow.

Review pipeline execution

Use View Run History to confirm whether individual executions succeeded or require attention.

Run history can include:

The execution date and time.
The run status.
The number of processed files or records.
The source integration.
Available error details.

This page covers pipeline management only. For detailed run-history, Background Processes, Audit Logs, Processed and Error folder behavior, and troubleshooting, see Monitor pipeline runs.

Delete a pipeline

Delete a pipeline when you no longer need its configuration or execution history.

When deleting a pipeline, Yarken removes the pipeline configuration and its run history.

Before you delete

Confirm that the pipeline is no longer required.
Confirm that no recurring business process depends on the pipeline.
If the pipeline was created through Automate, deleting it stops that automated upload workflow.
Record any configuration details that you may need to recreate later.

Delete the pipeline

Find the pipeline you want to remove.
Select the Delete icon.
Select OK on the confirmation message.

Deleting the pipeline removes the dependency on its Data Mapping Template. You can then remove the template if no other active or inactive pipeline references it.

After you change a pipeline

After you edit, reactivate, or run a pipeline:

Review the next execution result.
Confirm that Yarken processed the expected source data.
For file-based pipelines, verify that the correct mapping was applied.
Open the destination Yarken feature and confirm that the expected records are available.
Refresh the affected cube when you need immediate reporting results.

Troubleshoot pipeline management

Issue	What to check
The pipeline does not run on schedule	Confirm that the pipeline is active and that the configured schedule is correct.
Run Once is not available	Confirm that the pipeline is active and that no other pipeline state prevents execution.
A run fails after you edit the pipeline	Review the updated connection, source path, mapping, selected API data, and schedule. Then check the run details.
Automate no longer runs	Confirm that the pipeline generated by Automate is still present and active.
You cannot delete a Data Mapping Template	Check for active or inactive pipelines that still reference the template. Update or delete those pipelines first.
The pipeline ran successfully, but the latest data is not visible in reports	Verify the destination data first, then refresh the affected cube if you need immediate reporting results.

Related content