The Data Products panel in General settings shows Dawiso’s Gate integration status. Gate is the external service that governs data products and output ports.
Test connection
Test the connection to confirm that Dawiso can reach Gate, reporting the detected version plus two channel rows: one for checkout requests, one for catalog sync. Use it after initial setup or any credential, URL, or network change.
Each channel row shows one of these states:
| State | Cause |
|---|---|
| Green | Verified: token issued, Gate accepted a write-free probe |
| Red: no token obtained | Identity service refused the request or was unreachable; check the connection to it |
| Red: token rejected | Gate refused an issued token; check Gate’s allow-list, expected subject, or scope grant |
| Hollow: unverified | Token issued, but the probe was inconclusive or didn’t complete. Not a failure and not a reason to rotate the credential: rerun once Gate responds |
The overall indicator turns green only when both signals are healthy and both channels are verified.
Metamodel readiness
The panel verifies metamodel readiness: the package must have the object, relation, and attribute types below for data product features to work.
- Gate sync:
data product,domain, andoutput portobject types, and thecontainsrelation type. - Create data product wizard’s Business Context step: the
use caseobject type, therelatedandhas labelrelation types, and theuse case descriptionattribute type. - Optional, for the classifications payload only:
confidentialityandPII-levelobject types and theirhas_*relation types.
The metamodel check describes your own metamodel rather than Gate, so it’s reported whether or not a Gate URL is configured.
A missing Business Context feature results in no selector or created use case.
Search readiness
The panel also checks whether the object pickers in the Data Product wizard (Business terms, Related data products, and Labels) can return results. The pickers query a different search index from the one behind the application search bar. They can come up empty even when search works everywhere else and every metamodel readiness check is green. The check reports:
- Which search form the pickers use, and the index that form reads.
- Whether that index name is one Elasticsearch accepts.
- Whether Elasticsearch actually holds the index.
- Whether every object type the pickers offer is imported into it.
- How many of your pickable objects are indexed, out of how many the index’s import rules should contain. Only objects on the main branch are counted; objects that exist only on concept branches are not.
A neutral ○ on any row means Elasticsearch could not be asked, not a failure.
The summary line distinguishes three outcomes:
| Outcome | Cause |
|---|---|
| Wizard pickers can search | Every check passed. |
| Wizard pickers return nothing | Invalid index name, a missing index or search form, or an empty index. Usually fixed by reindexing. |
| Wizard pickers miss some objects | The index holds fewer objects than expected. Reindex, or wait if indexing is still running. |
Last sync run
Use Sync with Gate to push the current state of domains, data products, and output ports immediately, outside the normal event-driven sync, after a bulk import or to recover from a missed update. Sync with Gate also retries the retirement of deleted data products and domains that are not yet retired; see Deleted data products and domains. This section reports the outcome of the most recent finished run, read from the stored result rather than a run in progress, so it stays available between runs.
The overview opens with summary counts, always visible whether or not the lists below are expanded:
| Count | What it counts |
|---|---|
| Delivered | Objects Gate accepted in this run. |
| Could not be built | Objects Dawiso could not turn into a Gate payload at all. |
| Not delivered | Objects Dawiso built but Gate didn’t accept. |
| Delivered without classification | Delivered objects with no confidentiality or PII-level classification attached. |
| Newly marked inactive by Gate | Objects Gate suspended for the first time in this run. |
| Newly marked active again by Gate | Objects Gate resumed in this run after a previous suspension. |
| Delivered with a port that has no linked data | Delivered objects with at least one output port carrying no bound data. |
Could not be built and Not delivered: two collapsible lists, each a table of object, reason, and recommendation, sorted by reason and then by object name. Each opens automatically when it has at least one entry, showing at most 50 entries plus a count of the rest.
| Reason | Recommendation |
|---|---|
| No owner assigned | Assign an owner to the object, then run the sync again. This applies to data products that are not deleted. A deleted data product without an owner is still retired in Gate. |
| Broken domain chain | Restore the object’s parent domain chain, then run the sync again. |
| Object no longer exists | The object was deleted during the run. No action is needed unless it should still exist. |
| Duplicate port name | Give each output port of this product a unique name, then run the sync again. |
| No connection covers this data source | Create a connection in Gate that covers this data source. |
| Source path cannot be resolved | Fix the path at the data source itself. Creating a connection in Gate won’t help. |
| Conflicting connection | Resolve the mismatch between the connection and the source path in Gate. |
| Ambiguous connection | Two connections in Gate share the same endpoint. Distinguish them in Gate. |
| Connection disappeared during the run | Run the sync again. This state is usually transient. |
| Dependency not delivered yet | Deliver the parent domain first, then run the sync again. |
| Unknown sync run | Start a new sync run and send the object again. |
| No response from Gate | Gate didn’t answer. Check that Gate is reachable, then run the sync again. |
| Access Gate rejected the request | Access Gate refused the data Dawiso sent. The details are in the object’s last error; Dawiso retries the next night. |
| Connection could not be resolved | Gate couldn’t resolve a connection for this port. Check the connections covering this data source in Gate. |
| Metamodel is incomplete | This installation is missing a metamodel entry the sync requires. Check that the Data Products package is installed correctly. |
| Unrecognized reason | Gate reported a reason this version doesn’t recognize, or Gate accepted the push but did not apply the content (shown as “Gate did not apply the content”). Check the Gate logs for this object, then run the sync again. |
The panel also reports the state of the run itself:
| What you see | What it means |
|---|---|
| No run has completed yet | The channel has never finished a run. |
| A positive message inside an empty list | The last run succeeded and that list is genuinely empty, not the same as never having run. |
| The run didn’t complete cleanly, followed by a reason | A degraded finish: a Gate failure, an incomplete delivery, or an abandoned run. The reason appears below the notice. |
| The report couldn’t be read back | The result couldn’t be read back, so the outcome is unknown. Reported separately rather than as a clean run, since the counts would otherwise read zero. |
| Gate was not told the delivery is complete this run | The channel hadn’t yet delivered any object when the run started, so Gate skipped its own absence check for that run. |
If the overview fails to load, the panel offers Try again, except on a permissions error, where retrying would only reproduce it.
Deleted data products and domains
Deleting a data product or domain in Dawiso retires it in Gate, so Gate stops offering it for access requests. Gate keeps the record and marks it as retired. This applies however the object is deleted:
- Deleting the object directly, including data products inside a deleted domain.
- The Delete object automation action.
- Deleting or rolling back a package.
- Deleting a space.
- Removing the application from a space.
Data products are retired first, then domains.
The retirement is best-effort. It includes the owner, name, and domain only when Dawiso can resolve them. If the deletion also removed the owner relation, Dawiso uses the most recent former owner. A deleted data product that never had an owner is still retired, and it does not show as No owner assigned in the sync report.
Retiring is final in Gate. A data product or domain that is restored in Dawiso after deletion, for example when a package version brings it back, stays retired in Gate. Gate refuses its later updates. When Gate reports an object as retired, Dawiso marks it as retired in Gate and stops sending it. To get the object into Gate again, re-create it in Dawiso; the new object gets a new identity. Contact support or your administrator if you need help.
If Gate is unreachable or returns an error during the retirement, Dawiso retries it automatically. Sync with Gate and the nightly sync both start with a retirement sweep that retries every deleted data product and domain not yet retired, data products first. The sweep runs within a time budget, 900 seconds by default (be.integration.gate.sync.retire_sweep_budget_seconds). Objects the sweep does not reach in time are handled in the next run. If Gate rejects a retirement, the reason appears in the object’s last error.