| Level | Event / Error | Description | Example (“Details”) |
|---|---|---|---|
| Info | Consolidation start | Start of diagram consolidation | Diagram incoming. Got [number] assets and [number] relations. |
| Info | Consolidation end | End of diagram consolidation | Diagram outgoing. Forwarding [number] valid assets and [number] valid relations to upsert. |
| Info | ”Empty data” or ”nodes and edges empty” | Nodes and edges are empty making the consolidation and “upsert” (update/insert) step obsolete. | No assets to process. Aborting … |
| Info | NEW_RELATION_CORRECTION | Newly incoming edge with valid source and target has a relation name whose source and target type names do not fit the referenced source and target IDs. | There are relations whose relation type in the incoming data does not fit the referenced source or target element types. The relation types are corrected accordingly. [List of assets] |
| Info | Pre-processing starts | Data incoming. Got [number] assets (among [number] element types) and [number] relations (among [number] relation types). | |
| Info | Pre-processing finished | Data outgoing. Forwarding [number] valid assets (among [number] element types) and [number] valid relations (among [number] relation types) to upsert. | |
| Info | RELATION_CORRECTION | An incoming edge is already persisted but has a source or target that was merged into another type. | There are relations whose relation type in the incoming data is different than their persisted relation type. That can happen when the persisted relation has a source or target that has been merged with an element of a different type. The affected relations’ types will be changed to the persisted relations’ types to ensure compatibility between incoming and persisted data. [List of relations] |
| Info | TYPE_CORRECTION | An incoming node is already persisted but has been merged into another type. | There are assets whose type in the incoming data is different than their persisted type. That can happen when the persisted element has been merged with an element of a different type. The affected assets’ types will be changed to the persisted assets’ types to ensure compatibility between incoming and persisted data. [List of assets] |
| Warning | CASTING_FAILED | Casting a property into a target data type failed due to type incompatibility. | There are properties whose value cannot be cast to the intended data type. [List of properties] Loss of information can be avoided by sending properties with consistent and compatible data types. |
| Warning | CASTING_SUCCESSFUL | Casting a property into a target data type succeeded. | Property values were cast successfully to a suitable data type. [List of properties] |
| Warning | EDGE_WITHOUT_NODE | Edge references a source/target that does neither occur in the incoming nor the persisted data. | There are relations without a source or target element. [skipped assets] Relations must have a source and target element, either in incoming data or already persisted. |
| Warning | INTERNAL_ID_NOT_FOUND | Node or edge has an internal ID but that ID for a node or edge does not exist in Qbilon. | There are assets that could not be found via their ‘qbilonId’. Make sure that the Qbilon-internal IDs are correct and that the assets or relations exist. [Skipped Assets] |
| Warning | JSON_PROPERTY_NAME | A property’s key and name do not match. | There are malformed properties! Keys must match their name. The properties’ keys are used as name to ensure distinct property names. [Number of assets] assets with IDs [List of IDs] of types [Types List] have properties with names [List of properties] that are affected. |
| Warning | MAJORITY_RULE | Data types are not explicitly defined, and were inferred. Data type inference yielded inconsistent data types. | Data types for incoming properties had to be inferred by their value. Results are inconsistent. The most common data type is chosen for these properties. [List of properties] Data types for properties should be consistent for an element type or a relation type to avoid loss of information. Set a data type explicitly for an element or relation type’s attribute to avoid data type inference. |
| Warning | NON_UNIQUE_ID | Qbilon ID or external ID are assigned to more than one element within its scope (IDs are expected to be unique within nodes and within edges, not globally). | There are assets with non-unique IDs. [Number] assets are skipped. Affected IDs: [List of IDs]. IDs must be unique. There are assets / relations with non-unique IDs. That can happen when duplicate IDs are incoming or when incoming assets have been merged within Qbilon and their IDs are now referencing the same element. [Skipped Assets] IDs must be unique. |
| Warning | PROPERTY_SKIP | A property cannot be cast to the target data type and is skipped. | There are properties whose value cannot be cast to the intended data type. These properties are skipped. [Number] assets with IDs [List of IDs] of types [Types List] have properties with names [list of properties] that are affected. Loss of information can be avoided by sending properties with consistent and compatible data types. |
| Warning | PROPERTY_VALUE_NULL | An incoming property’s value is null. | There are properties whose value is null. [List of properties] [List of assets] Loss of information can be avoided by sending properties with values. |
| Warning | PROPERTY_NAME_RESERVED | An incoming property’s name is reserved. | There are properties whose name is reserved for internal properties (reserved property names are: First Seen, Last Seen, Data Sources, Qbilon ID). [List of properties] [List of assets] Loss of information can be avoided by sending properties with other names. |
| Warning | QBILON_NAME_FALLBACK | A name-giving property is missing or not found. As fallback solution, the Qbilon internal ID is used. | There are assets / relations whose name-giving properties have been set but are not part of incoming or existing data. [number] assets with IDs [List of IDs] of element types [Types List] are affected.Their name-giving property will fallback to the Qbilon-internal ID. |
| Warning | UPDATE_STRATEGY_DISCREPANCY | The given update strategy is incompatible to the respective data type. | [Number of types] element types with names [List of names] have properties with names [List of properties] whose update strategies are incompatible with their incoming or already persisted data types: Update strategies [strategies’ names] cannot be applied to properties with data types [data type]. These update strategies are replaced with the update strategy [strategy name]. Please remember to apply list-specific update strategies only to properties with a list data type. |
| Warning | TRY_CASTING | There are type discrepancies between incoming and persisted data. | Incoming properties have different data types than already persisted instances. The incoming data will be cast to the persisted data type. [List of properties] |
| Error | edges: null | User explicitly sends invalid diagram object. The consolidation is aborted. | Incoming diagram shows significant format violations: ‘edges’ was null! Aborting pre-processing. Omitting ‘edges’ can be achieved by removing the property from the diagram entirely. |
| Error | nodes: null | User explicitly sends invalid diagram object. The consolidation is aborted. | Incoming diagram shows significant format violations: ‘nodes’ was null! Aborting pre-processing. |
6 – Data Sources
Warnings & Errors
Understand the messages reported by data source executions.
This table summarizes the messages that Qbilon shows after importing data from third-party systems (executing an automation task). They are available by navigating to the “Automations” section, clicking on a specific task and selecting the “Warnings & Errors” tab on the right:
