Skip to main content
Skip table of contents

Domo - Trigger Dataset Refresh

Overview

Manually trigger a refresh of a dataset in Domo. Authentication is serviced through a client ID and secret ID, similar to the use of the SDK. Both are required to authenticate. This Blueprint will only kick off the refresh and will almost always return a status of success. It will not wait around to verify if the created refresh job was successfully completed, but it will create and store the generated job ID to shipyard-artifacts/domo-blueprints/variables/job_id.pickle **Recommended Setup:** 1. A Vessel built with the _Domo - Check Refresh Status_ Blueprint should be run immediately after this Vessel. This will ensure that you build your Fleet to act on the final status of your refresh.

Variables

NameReferenceTypeRequiredDefaultOptionsDescription
Client IDDOMO_CLIENT_IDAlphanumericNone-Client ID of your organization's Domo App.
SecretDOMO_SECRET_KEYPasswordNone-Secret associated with the provided Client ID.
Dataset IDDOMO_DATASET_IDAlphanumericNone-UUID of the dataset you want to download, typically found at the end of the URL.
Wait for CompletionDOMO_WAITBooleanTRUE-Whether the blueprint should wait for the Domo refresh to finish. It is recommended to set this to TRUE.

YAML

Below is the YAML template

YAML

source:
  template: Domo - Trigger Dataset Refresh
  inputs:
    DOMO_CLIENT_ID:
    DOMO_SECRET_KEY:
    DOMO_DATASET_ID:
    DOMO_WAIT: 'TRUE'
  type: TEMPLATE
guardrails:
  retry_count: 1
  retry_wait: 0h0m0s
  runtime_cutoff: 1h0m0s
  exclude_exit_code_ranges:
    - 201
    - 203
    - 101
    - 106
    - 110
    - 111
    - 112
    - 113
    - 116
    - 115

      
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.