Schedule a Data Loading Process

Create a schedule to automatically execute an existing data loading process. You can configure a process schedule to run at a specified time or after another schedule, or to allow the schedule to be run only manually. Only one data loading process can be executed at a time.

You do not need to specify login credentials or be logged into the GoodData platform at the time of execution for a scheduled process to be initiated.

Schedule a Data Loading Process


  1. From the Data Integration Console (see Accessing Data Integration Console), click Workspaces.

  2. Click the name of the workspace where you want to create the schedule, and click New schedule

  3. Select the process to execute.

  4. Select the frequency of execution: 


  5. (Optional) Add additional parameters to your schedule. A parameter is a name-value pair that can be passed to the process before execution begins. If the process is designed to consume it, the parameter can be used to define variables specific to the execution. For example, you can define parameters for customer-specific login credentials for an external data source. For more information, see Configure Schedule Parameters.

  6. (Optional) Specify a new schedule name. The alias will be automatically generated from the name. You can update it, if needed.

  7. Click Schedule.  The schedule is saved and opens for your preview. The GoodData platform will execute the process as scheduled.

  8. (Optional) Click Add retry delay to set up a retry delay period for your schedule. When a retry delay is specified, the platform automatically re-runs the process if it fails, after the period specified in the delay has elapsed. For more information, see Configure Automatic Retry of a Failed Data Loading Process.

Schedule Owner vs. Process Owner

In the schedule details dialog, the listed user name identifies the user under which the schedule executes. This user currently owns the schedule.

Because processes can be downloaded and redeployed at any time, the owner of the schedule can differ from the owner of the process. For example, if a process created by User A is redeployed by User B, all schedules associated with the process are now owned by User B, who will be the user under which all schedules for the process are henceforth executed.