Star Wars API Dice Roller - Dice Image error only on the DicePool sheet

Hello everyone, I have an issue that I can fix concerning the dicepool sheet. All the dice image won't appears on it. Everything else is working else, I have no image issue when the dice appears on the party chat. I've tried restart the sandbox or test new script but nothing change. Do you know how to fix it ? Here an image of my problem

Hi Clement, The API dice roller for the sheet was recently fixed to address broken images.  This was fixed by using images that hosted on Roll20's repo.  Some UK and other regions have been experiencing broken images when those sheet images are hosted off-Roll20.  I just checked the sheet code for Star Wars: FFG (API-Compatible), and it appears that all the images for the sheet are indeed being hosted on Roll20, so that should not be a problem. I can see the dice images using FF on win, so there may be something else going on. Are you using the production/live version of the FFG API- compatible sheet or a custom game?  If so, I would suggest changing the game's sheet template to the "Star Wars: FFG (API-Compatible)" listed in the drop-down list from the game settings page. (as a precaution, you may want to try this on a copy of the game first)  Or are you using a different version of the FFG sheet by chance?

Thanks for your answer, I was indeed not using the right game sheet. With the Star Wars FFG API compatible the images are back on the dice roller. I made the switch but now I have this kind of messages in the game chat when the dice are rolled for all the agility and brawn checks and I don't how to proceed to fix this issue. And sometimes I also got this message :

Glad you've got the correct sheet with working images now! This new error you are seeing is a current Roll20 bug .&nbsp; Another Star Wars sheet user reported the same error <a href="https://app.roll20.net/forum/permalink/12721278/" rel="nofollow">https://app.roll20.net/forum/permalink/12721278/</a> &nbsp;It has been reported to roll20's help desk (#458703) and I was told Thursday that the Devs are working on a fix.