Skip to main content
Status messages appear in Studio to indicate what Prophecy is doing behind the scenes as you make changes or run your pipeline. You’ll see these messages in the bottom-right corner or the center of the Studio canvas.

​
Reference

You’ll see the following messages in Studio.
MessageDescription
Initializing projectProphecy is loading project files and setting up the Studio environment. This message blocks interaction with the canvas until initialization completes.
Processing changesProphecy 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 codeProphecy 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.
CompilingProphecy is performing checks and computing output schemas for each gem’s output. Compilation happens automatically after code generation.
DBT initializationProphecy 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.
RunningProphecy is executing your pipeline. This includes orchestrating the run, managing dependencies, and coordinating execution across different components.
Running query in warehouseProphecy 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.

​
Duration

Status messages may remain visible longer in large projects because:
  • More gems require more code generation.
  • Complex dependencies need more processing time.
  • Larger schemas take longer to compute.
  • More files need to be synchronized with the dbt sandbox.
If a message persists for an unusually long time, try refreshing the page. If the problem persists, contact support.