import export

Workflow import is not valid JSON

The selected file could not be parsed as a DecaCap session or configuration.

Curious Obmil examines three clearly separated illuminated diagnostic paths inside a brass-and-crystal crossroads
Decode the cause before choosing the response.
MATCH THESE VISIBLE STRINGS
  • The workflow request is not valid JSON.
  • Unexpected token in JSON
  • Unsupported workflow file
LIKELY CAUSES
  • File was edited into invalid JSON
  • A Markdown export was renamed to .json
  • The configuration schema is unsupported
  • The upload extraction returned no JSON text
NEVER DO THIS
  • Do not paste provider secrets into a configuration
  • Do not bypass locked-box entitlement checks
SMALLEST DIAGNOSTIC FIRST

Repair sequence

01

Use a file downloaded from the recipe library or Workbench

02

Confirm the extension and MIME type

03

Open the file in a plain-text editor and validate JSON syntax

04

Keep provider keys and pairing tokens out of configuration files

05

Import again after validation