Skip to main content

Managing Refresh Jobs in Failed a Deployment Environments

Issue​

  • Problem: Unable to run refresh jobs when the target environment deployment is in a failed status.
  • Context: Not all jobs require deployment and you need to run jobs independent of deployment status.

Solution​

Fixing the Deploy is Recommended

We recommend fixing the deployment, instead of ignoring the failed state. Only use the provided solution if you are sure this is the best path. Use caution when using the forceIgnoreWorkspaceStatusflag and confirm that the nodes in the job you want to refresh are unaffected by the failed deploy.

Use the forceIgnoreWorkspaceStatus flag. This flag will allow refresh jobs to proceed even when the environment is in a failed state, targeting unaffected parts of your Directed Acyclic Graph (DAG).

API​

Review Start Run.

curl --request POST \
     --url https://app.coalescesoftware.io/scheduler/startRun \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{
  "runDetails": {
    "parallelism": 16,
    "forceIgnoreWorkspaceStatus": true
  },
  "userCredentials": {
    "snowflakeAuthType": "Basic"
  }
}
'

CLI​

Review COA refresh options.

coa refresh --forceIgnoreEnvironmentStatus true