Skip to main content

Operations and troubleshooting

Understand the three versions involved​

When behavior is unexpected, identify:

  1. the version open in Designer;
  2. the version deployed in the selected environment;
  3. the versions of every dependency referenced by that deployed item.

Testing Zone and the execution API use deployed versions. A successful save proves only that the editable definition was stored.

Trace an execution​

Start with the correlation ID. Search Organization → Execution History, inspect input/output, and open Debug Data if captured. For workflows, follow the ordered node trace and compare each mapped input with its output. For event nodes, continue to Integration Activity and connector health to inspect delivery, retry, or dead-letter state.

Common causes​

  • Wrong active organization, solution, or environment.
  • Missing permission or inactive membership.
  • Input no longer matches its Data Model.
  • Workflow edge mappings point to renamed fields.
  • A dependency version was not promoted.
  • A Global Variable has no value in the environment.
  • Connector configuration exists in Development but not the runtime environment.
  • API key is expired, revoked, rate-limited, or belongs to another environment.
  • Analytics was enabled at only one of its two required levels.

Safe maintenance​

Export important HubItems before large refactors, create a version boundary, review dependency analysis, run saved tests, and use deployment requests. Apply retention policies and delete versions only after reviewing their irreversible impact.

DecisionHub does not expose a user plugin SDK, plugin marketplace, arbitrary runtime package installation, or general webhook/GraphQL configuration in the documented interface.