Known Issues for MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

• A sporadic failure may occur when inviting a User via the Identity Management Service. The current workaround is to reinvite the User.

• After modifying the authorization of a User via Identity Management Service, the change is not immediately visible. The User must then close the browser and login again.

• For security reasons a strict timeout is enforced. Currently this leads to the situation that the size of a file which can be uploaded/ downloaded depends on the network bandwidth at client side.

• When uploading files to the File Service, a file name must not contain blank spaces. Blank spaces in the file name will prevent the file form being stored.

• When querying raw time series data that is older than one week, the 'SELECT' query parameter has no effect. The query will always return all properties.

• A limit on retrieving raw time series data is currently not enforced. We recommend paying attention to the amount of data requested; this might lead to increased response times.

• In order to delete time series data, the 'FROM' and 'TO' parameters must have different values; the 'FROM' parameter needs to be at least 1 ms less than the 'TO' parameter.

• When sending time series data without '_time' field in body of the service request, the service returns a 500 error code instead of a 400 error code.

• When sending time series data to a non-existing entity, the service returns a 500 error code instead of a 404 error code.

• The maximum payload size of a message sent to time series service as part of a PUT request cannot exceed 1 MB.

• Push notifications shall not be used for time sensitive applications as MindSphere does not own the total chain of communication.

• Encrypted mails must only contain ASCII characters.

• Hysteresis filter is currently disabled.

• Sporadically streams cannot be deleted. Please try again if it was unsuccessful.

• If an entity is derived from type core.basicdevice only one stream can be deployed.

Aspect Types, Asset Types and Assets should not start with a leading number in their name.