Dear Cindy, 
Greetings of the day

I would recommend to update to the latest stable version of both the plugins from outsystems forge & then refresh your dependent modules. 

If still the issue persists, then I would suggest to add your issue / comment in specific forge component itself. 
So that component owner/team members are notified & they can work upon that issue. 

Let us know if that works for you. 

Regards,

Palak Patel

Hi Palak,

Maybe I have missed out some steps if you can show me the step by step or any link that can guide me on updating both plugins from Outsystems forge and also refresh my dependent modules?

I captured Manage Dependencies pages for your reference.

Hello Cindy

The steps you have posted are to refresh the dependency in module while what Palak is suggesting is to update the component from forge. 

Please go to forge from Service Studio, Search For Plugin, and you will see option to update it. If you find this is updated, you will need to publish the Force itself in your environment. 

May be, it is installed there but not published in your environment correctly. 

Let us know in case you still have doubts.  

Hi Manish,

Thanks for the advice.

If the forge shows the plugin are updated, so how do I publish the plugin by force in my environment? 

How do I verify the plugins in my environment are published correctly as my first message they will prompt me to clone the plugin?

Hi Cindy, 
From you modules in service center, are you able to see the consumers of these plugins are outdated or not updated ? 
If so, I would recommend to republish these plugins from service center or click Publish All Consumers. 
By this way, you will be able to publish all dependent modules and republish the components itself in your environment. 

Regards,