| Initializing project | Prophecy is loading project files and setting up the Studio environment. This message blocks interaction with the canvas until initialization completes. |
| Processing changes | Prophecy has received your edits and is checking for side effects that need to be handled. The system identifies dependencies and updates related project files automatically.
For example, adding a table from the Environment tab to the pipeline canvas also creates an entry in sources.yml. |
| Generating code | Prophecy is converting your visual pipeline into SQL files. During this process, Prophecy: - Scans all gems in the current pipeline for changes.
- Generates SQL code for each gem.
- For custom macro gems, executes the
apply method you implemented in a separate sandbox environment.
Code generation runs automatically when you modify gems. Duration depends on the number of gems and complexity of transformations in your pipeline. |
| Compiling | Prophecy is performing checks and computing output schemas for each gem’s output. Compilation happens automatically after code generation. |
| DBT initialization | Prophecy is preparing the dbt environment for your project (since Prophecy uses dbt behind the scenes for transformations). Before running pipelines, Prophecy: - Creates a sandbox environment loaded with all project files.
- Updates the sandbox with recent changes.
- Compiles models using dbt to produce final runnable SQL code.
This message appears when you start a pipeline run. |
| Running | Prophecy is executing your pipeline. This includes orchestrating the run, managing dependencies, and coordinating execution across different components. |
| Running query in warehouse | Prophecy is executing SQL queries directly in your data warehouse. Different parts of your pipeline run in different environments: - SQL transformations execute in your SQL warehouse.
- Orchestration, data ingestion, and data egress operations run through Prophecy Automate.
|
