Skip to main content
· 4 min read

July 2023 new features, fixes, and improvements

New features

  • 🌮 Customers are now able to create sample data with the new TacoSoft Data Source.
  • 🟣 New Console look and feel.
  • 💦 The UI Kit supports a new prop, refetchInterval, which can be used to specify how frequently a component should re-fetch new data.
  • 📦 We have simplified UI Kit and re-packaged it as a single, tree-shakeable NPM library, @propeldata/ui-kit.


  • In the Metric Playground, we fixed an issue with the filter drop-downs not showing values. Customers can now select a unique value from the drop-down when using filters in the Playground.
  • Fixed an issue with unique name-checking. Customers will now see validation for every unique name in the console.
  • Fixed a bug in the Metric Report API where users could select dimensions not declared in any of the report's Metrics. Now developers are only able to select dimensions specified in the Metrics.
  • Fixed a Counter Metric performance regression.
  • Fixed a corner case where new Data Pools were getting stuck in the "CREATED" state.
  • Fixed a bug where if a measure or dimension column in a Metric is JSON, we were not taking it into account as part of the available columns to be selected.
  • Fixed an issue with the calculation of query timeouts. Some queries were incorrectly timing out at 3 seconds when they should time out at 10 seconds.
  • Fixed a password reset bug.
  • Fixed an issue where we were missing time granules for certain relative time ranges.
  • The Amazon S3 Data Source now supports syncing larger S3 buckets, and will sync up to 1,000 files at a time.
  • Previously, S3 Data Sources could be created with invalid S3 bucket names, resulting in them getting stuck in a "CONNECTING" state. Now, when attempting to create or modify an S3 Data Source, setting bucket to an invalid S3 bucket name will result in synchronous failure with a BAD_REQUEST error message: "Invalid S3 bucket name; ensure you pass only the S3 bucket name and not its ARN or URL".
  • Customers can now switch tables and see the updated schema when creating a Data Pool. Previously, the schema was not updated when switching tables.


  • New homepage with a handy video!
  • In the Data Pool section of the Console, we have improved the Sync error messages for Snowflake and S3 Data Sources. Customers will now see a helpful message with the error details for failed Syncs in the Data Pool overview syncs table.
  • In the Metric definition, Metric settings, and Playground sections of the Console, the filter operators IS_NULL and IS_NOT_NULL are now available.
  • In the Data Pool section of the Console, the "Preview Data" table now loads faster and adjusts to the screen height. Additionally, the text in the cells of the table will not wrap, and an ellipsis will be displayed when the text is too long.
  • In the Data Pool section in Console, we updated Data Pool documentation links.
  • We have improved API error messages for our customers. Authentication and authorization-related errors and identifier parsing errors will no longer be returned as internal errors. Instead, we catch these errors and provide more informative error messages.
  • We have improved the handling of query errors by introducing a new error that specifically indicates when the Propeller is too small. If a Metric query exceeds the maximum execution time, customers will now receive a more informative error message. The message will indicate that the user needs a bigger Propeller instead of a generic error message such as "The query failed for an unknown reason.”
  • Data Pool Syncs are now created before attempting to connect to the underlying database, resulting in earlier visibility. Previously, if we failed to connect to a database, we did not create any Sync and kept retrying until successful. With the new process, we create failed Syncs that represent unsuccessful attempts, improving visibility for customers.
  • The Console now remembers the last environment a user accessed when switching between accounts.
  • The Console now remembers the last account and environment a user accessed when logging back in.
  • If a user has never logged in, the Console defaults to their most recently created account and its development environment.