Apps in Legacy Flows and Flows Are Getting More Reliable (No Action Needed)
We're making a technical improvement to how Apps run inside your legacy flow and flows. No action needed on your side. Your workflows will keep working exactly as they do now.
What's changing
When you use an App as a task in a legacy flow or flow, we're switching to a more reliable way to start it. You won't notice a difference — everything works the same way for you — but behind the scenes, we're using a newer, lighter component built specifically for this job.
If your legacy flow or flow starts an App as one of its tasks, that task currently runs through the legacy keboola.data-apps component. In the coming weeks, we'll be migrating these tasks to use keboola.data-app-control instead.
Why the change?
keboola.data-apps relied on the legacy Sandboxes API to start the app. We built keboola.data-app-control as a lightweight, purpose-built replacement for exactly this use case — starting an App as a task in an orchestration or flow — and it's what now replaces the old mechanism there.
What this means for you
- No action is needed on your side. We'll run this migration ourselves, stack by stack, over the coming weeks. Your orchestrations and flows should keep working exactly as before. If we come across a configuration that can't be migrated automatically, we'll reach out to you directly.
If you notice anything unexpected in a legacy flow or flow that starts an App after this change, please reach out to our support team.