Skip to main content

Known limitations

As we build and grow Astro, our team is committed to maintaining transparency about the current limitations of the product as well as the roadmap ahead of us.

The list below represents known issues at the time of writing. We're moving fast to address these and are excited to work with you to identify solutions to some of these foundational questions.

If you have questions or feedback about any item below, reach out to your Customer Success Manager.

Known limitations

  • In order to invite a user to a Workspace, the user must already be a member of the Organization as described in Add a user.
  • If a user changes Workspace roles on Astro, it can take a maximum of 10 minutes for corresponding Airflow permission changes to take effect.
  • Astro supports only the Celery executor. If you currently use the Kubernetes executor, you might have to modify your tasks to run on Astro.
  • Clicking on Refresh DAG in the Airflow UI will redirect you to <org-name> (Astro Home Page) instead of the task instance URL. We recommend upgrading to Runtime 4.0, as Airflow 2.2 no longer requires this refresh button in the Airflow UI.

Coming soon

  • Workspace API keys that are accepted by the Astro CLI and can be used to automate the creation and deletion of Deployments.
  • A new executor built by Astronomer that will offer intelligent worker packing, task-level resource requests, an improved logging system, and Kubernetes-like task isolation.
  • The ability for Organization Owners to create a cluster without Astronomer's assistance.