CARTO Workflows is currently in public beta, what are the plans to release the first version as “general availability”?

We plan to release the first official version of CARTO Workflows to general availability by the end of March 2023.

When will CARTO Workflows become available for Snowflake, Redshift or PostgreSQL connections?

We plan to release in public beta CARTO Workflows running on Snowflake, Redshift and PostgreSQL during February 2023.

Is CARTO Workflows available in self-hosted deployments?

CARTO Workflows will be available for self-hosted deployment as soon as we launch the tool to general availability, which it is planned for March 2023. Please contact [email protected] if you would like to have more information about this topic.

Do I have to pay more to be able to use CARTO Workflows?

No, CARTO Workflows is a core tool of our platform and it is available in all subscription plans. Running workflows, in the same way as building and using maps, will have an impact on the computing processes that you execute in the CARTO platform and in the associated cloud data warehouse, which may be subject to specific usage-based quotas.

When creating a new workflow, I cannot see the data sources available in my connection - what may be happening?

This may be because the data warehouse connection associated with the workflow does not have the required permissions to run Workflows in the data warehouse, such as the permission of creating schemas in the Workflows temp. location (configured in the advanced options of the connection card). Please choose or create another connection with data owner permissions or modify the permissions in the current connection and try again. If the issue persists, please contact our support team at [email protected]

Why if I copy the SQL code of my workflow (available in the preview panel) and I execute it directly on my data warehouse console it does not run properly?

This is due to the fact that the SQL code showcased in the Results panel is a simplified version of the code required to execute the workflow, for debugging and illustration purposes; but it does not include all control statements and elements that we add on the actual SQL code to execute it in your data warehouse. This is a user-friendly version of the SQL code so the user can get a high level idea of the main SQL statements that build up the workflow that it’s been designed.