In some cases, a Stitch workflow may appear to complete successfully when you open the workflow details, but the overall workflow status in the UI or API is shown as Failed. This behavior is usually caused by hidden Analyst Enablement tasks failing in the background.
Symptoms
Stitch workflow status is Failed in the Workflows page or via API.
When clicking into the workflow, all visible Stitch steps appear to have completed successfully.
No obvious error is shown in the default workflow view.
Root Cause
Amperity Stitch workflows may include Analyst Enablement tasks, which are:
Hidden by default in the UI.
Responsible for publishing output database tables to Databricks.
If these tasks fail, the overall workflow status is marked as Failed, even though the core Stitch process itself may have succeeded.
These tasks typically fail when the service account or user executing the workflow does not have sufficient permissions in Databricks, such as:
Creating schemas in the target catalog.
Accessing or using the specified catalog.
How to Identify the Issue
Open the affected workflow.
Enable the option to show Analyst Enablement tasks in the workflow UI (this option is disabled by default).
Review the newly visible tasks.
Check the error message for permission-related failures such as:
Cannot create schema in catalog.
Permission denied to access or use catalog.
Resolution
Update Databricks permissions for the user or service account running the Stitch workflow to ensure it can:
Access and use the target catalog.
Create schemas within that catalog.
Write tables to the required database/schema.
After updating permissions, rerun the workflow and confirm that all Analyst Enablement tasks complete successfully.
Additional Notes
Even if Stitch completes successfully, the workflow will remain in a Failed state until all hidden Analyst Enablement tasks are resolved.
This issue does not indicate a problem with Stitch processing itself, but rather with downstream publishing permissions.