When triggering the concurrent subscriptions to publish a cube with different database connections, some of them do not publish.
DSSErrors.log, you can see the following error.
2020-05-12 10:33:57.480 [HOST:env-208313laiouse1][SERVER:CastorServer][PID:5881][THR:140306529990400][Distribution Service][Error][UID:47F7756B11EA934D99260080EFC51F7D][SID:1939B862D99CD23C086BF6D702CE5C4B][OID:A04679004A1C9B487543859DB6267C0F] FAILED SUBSCRIPTION. Subscription 'Access_transactions_test7' (ID = 65FA6FDB11EA93FD41550080EFA57FCF), Contact 'test7' (ID = 47F7756B11EA934D99260080EFC51F7D) Schedule Execution ID = 15A12CCE11EA943C0FA50080EF857C3D User (test7, 47F7756B11EA934D99260080EFC51F7D) Error Message: MSIJob Execution Error: Job ID = 78, Comp Error code = -2147072550; Error Code 0x800437FD: (Error in Process method of Component: CubeServer, Project Strategy Tutorial, Job 78, Error Code= -2147072550.) Stop in 'hPreTransmissionNotificationWithErrorCode, Delivery Component of Distribution Service'
From the log, you can see the error code is -2147072550, which means the Cube Manager fails to create an entry for the new cube cache in this job. This can happen to concurrent publishing of a cube that was never published before.
To ensure all the cube caches are published in the subscription, you should use one user to publish the cube first, prior to triggering the subscription.