The last charge event received for charge resource /company/03638935/charges/tYJDs7lTHdy1JYtQdNSASi8Axf8 does not match the response from the REST API for that charge. The etag is different between the two responses with the most recent etag to have appeared in the stream being “15adabb4fa2dfdc065f00d657f73b92f2bd18711” whereas the REST API is currently (and at least since 23:05 11/11/24) returning “cf73d418b0908a11f6b3ffa0ef2ac62a65c751b7” which is particularly confusing as there don’t seem to have been any changes to any of the data fields.
Please can you confirm what’s happened here?
Apologies for this. We have found an issue. Performance improvements we have applied to our services recently, have caused timing issues. A workaround has been put in place to reduce these occurances, while a full solution is being worked on.
Hi Mark, is there any update on when the full solution will be ready?
We’ve been noticing the latest stream events don’t match the REST API for both companies & officers
Hi Mark,
Can I ask what sort of timescale we might be looking at for the fix? Alternatively, if that is uncertain, do we know what the extent of the issue is? If the exact behaviour with the issue is known, then perhaps we can implement a workaround on our side in the meantime. Thanks for your help, it’s really appreciated 
