Fallback Behavior

If a project can’t find a matching catalogue row for the current conditions, or if the catalogue API call fails for any reason, the system automatically displays the original layers from the project.

This ensures the playable always renders correctly, even when:

• The user’s conditions don’t match any configured row (for example, an unlisted region or temperature).

• The catalogue is unpublished, unavailable, or has missing values.

• The user has a slow internet connection and the API call fails and/or times out.

How It Works

• When the project loads, the system checks the catalogue for a matching row based on the active conditions.

• If none is found, or if the request fails, the catalogue simply skips the dynamic substitution step.

• All layers display their original, static values as defined in the project file.

Think of the catalogue as an extra “bonus” layer added to your creative. If it fails for some reason, the base creative is still there as a fallback.

What this means: Your creative always loads no matter what!