Known Issues
These issues are currently known and under active work. Most are runtime failures where the affected execution recovers on a retry, so the fastest path is usually to retry the failed run and confirm it completes. Where a retry does not apply, the workaround column says what to do instead.
Last reviewed at the most recent release. Statuses change as fixes are validated and promoted, so check the release notes for the version you are running.
Current issues
| Status | Issue | What you see | Cause | Workaround |
|---|---|---|---|---|
| 🟢 | Subflow not loaded | An execution fails because a referenced subflow is not loaded correctly at runtime. | Workflow unloading in the runtime engine. | Retry the failed run. |
| 🟢 | Resource not found | An execution reports that a required runtime resource cannot be found, even though it is configured correctly. | Workflow unloading in the runtime engine. | Retry the failed run. |
| 🟢 | Unable to load due to MetaSpace issue | A workflow fails to load or to continue executing. | Runtime engine MetaSpace management. | Retry the failed run. |
| 🟢 | Data table query (DTQuery) issue | A data table query fails during execution because the required runtime resource is unavailable. | Workflow unloading in the runtime engine. | Retry the failed run. |
| 🔴 | Unable to connect to SFTP | An SFTP activity fails when the connection to an external server times out. | Timeout reaching the external SFTP endpoint. | Retry the failed run. If it persists, confirm the external SFTP endpoint is reachable. |
| 🟡 | Lookup value not refreshed immediately | A recently updated lookup value is not reflected in the next execution. Rare. | In a multi-engine setup, an engine can briefly serve a cached lookup value after an update. | Retry the failed run. The retry uses the refreshed value. |
| 🟡 | Local schema duplicated in a workflow | A local schema appears twice in a workflow. Reported once; not currently reproducible. | Not yet confirmed. Suspected to involve importing or exporting an application or workflow. | Delete the duplicate schema. Before reporting, note whether the workflow was imported or exported beforehand — that detail is what the investigation needs. |
What the statuses mean
| Status | Meaning | |
|---|---|---|
| 🟢 | Fix in validation | A fix is deployed to the Development environment and is being validated before promotion to Production. |
| 🟡 | Under investigation | The cause is not yet confirmed. Debugging is in progress. |
| 🔴 | Open | The issue is known and reproducible, with no fix currently scheduled. |
Runtime fix status
A runtime engine fix covering workflow unloading and MetaSpace issues is deployed to the Development environment. That fix addresses four of the issues above — subflow not loaded, resource not found, MetaSpace load failures, and data table query failures.
It is being validated now and will be promoted to Production once validation succeeds.
Retry a failed run
- Open the failed execution.
- Read the failure message and check it against the table above.
- Retry the run.
- Confirm the retried execution completes successfully.
If the same failure repeats after a retry, it is unlikely to be one of the transient issues listed here. Contact support with the execution details and the failure message.
Reporting an issue not listed here
For a failed execution, include the execution ID, the workflow and application names, the failure message, and the approximate time of the run. Those four details are usually enough to identify the cause without a follow-up round trip.
For something wrong in the workspace rather than in a run — a duplicated or missing item, for example — include the application and workflow names and what you did immediately before noticing it. Whether the application was imported, exported, or cloned is often the detail that identifies the cause.