Skip to main content

Publishing errors

Publishing validates the whole card more strictly than ongoing editing. A draft is allowed to be half-finished; a live version is not.

”Add at least one building block”

A blank card can be saved but cannot be published. Add at least one visible building block.

A building block is invalid

Click the issue indicator. Typical block errors are:
  • a Report is missing its report number;
  • an Image has an invalid URL or empty alternative text;
  • a Table, Chart, or Repeater points to a missing list;
  • an input’s options are missing, or manual and dynamic options are mixed;
  • a minimum limit is higher than the maximum;
  • two input fields share the same internal field key;
  • a building block is not allowed in the placement.

Unknown data source

A binding or action points to a source that has been removed. Select the field/list again, or reconnect the system. Repeat for visibility rules and action values; they can hold references too.

Invalid row field

A Row field can only be used on a child block inside a Repeater. Move the block back, or choose a normal record/connector value.

Invalid selected-record field

A Selected [object] value requires a dropdown/multiple choice/button group field with options from an association data source. Check the input field’s options source.

Step errors

Check that:
  • a step-assigned building block points to an existing step;
  • required fields still exist;
  • “go to specific step” points to an existing step;
  • flow actions are only used when steps are enabled;
  • the flow has between 2 and 12 steps.

Action errors

  • Open a link must be the last action in its list.
  • Conditional branches can be nested at most two levels deep.
  • Record a choice must point to an existing input field.
  • Connector and refresh actions must not point to a removed source.

Configuration too deep or too large

Building blocks can be nested at most four levels deep. A card can have at most 100 blocks, 20 data sources, and a serialized configuration of at most 100 KB. Reduce repeated or redundant content, remove unused data sources, and split very large user flows across multiple cards.

”Another card is already live”

A live card occupies its combination of placement and object type. The error text names the colliding card and the overlapping objects. Take the existing card offline, choose a different placement, or remove the overlap in objects. There is no automatic overwrite, because that could take an active card out of service without a clear decision.

Preflight is green, but runtime fails

Preflight validates the configuration, not every external permission and data point. Check HubSpot scopes, user permissions, report access, connector credentials, and that the expected fields exist in the specific portal.