Hey @Manasi_Panov thanks for your response, were you able to find a workaround to resolve this issue from the domo support or is it a bug specific to the instances that needs to be updated from their end?