Localization Framework Hub and Spoke architecture - retranslation

[Hardik10]

I have implemented Hub and Spoke architecture for Localization framework. The key problem I came across is when the value of the field is changed. 

For example: Catalog Item has Name and short description field. When we create a new record and then request for translation, the spoke instance will send to hub and retrieve translation from hub. Then we publish it. In Hub, we have set auto-translate and auto-publish. 

Now, later stage, we need to make a small change to Name or short description and we will request the translation again. This will send the text with its translated value in payload to hub. Hub will see that this record already has the translated value, and it will not re-translate it. Now, even in spoke instance, I remove the lock and retrieve the translation, it will provide me the old translation only from Hub. So, this looks like a limitation that it will not be able to identify or not allowing to re-translate. This would be bigger challenge as the some of data keep changing, of course not frequently.

[Hardik10]

@Alex Coope - SN , do you have any thoughts or any idea on above questions?

[Alex Coope - SN]

hi @Hardik10,

Thanks for making me aware of this. I think I understand what's happening here. I'll raise it with the team and see what options we can provide going forwards. Just to set expectations, it might not be a quick answer on this one I'm afraid,

Many thanks,
Kind regards 

[Hardik10]

Thank you @Alex Coope - SN .

when you have something on this, could you please reply if possible, so that I am aware and take decision on using Hub and spoke architecture.  

[Hardik10]

@Alex Coope - SN , Also, without Hub and Spoke, is there anything we can do to force Machine translation to translate the content if the English version of content is changed? Or kind of invalidate the existing translated text? I can write BR on record change to find the specific records in the one of the translation tables, but I need to implement for all the tables where we have translation enabled. 
This is needed for auto-translate and auto-publish flow as there won't be any human in the loop.