Hello everybody @here
There’s been a very understandable amount of concern among Make/Xero users on this issue. While we’ve been working hard on identifying and resolving the problem, we could have done a better job of communicating with you all on this. For that, we’re truly sorry.
We recognize that Xero is an important system of record for many users and that the smooth running of workflows involving Xero is often of vital importance. The level of concern shown on this Community (and in reports to our Support team) reflects that.
Our core engineering team has been working hard on this since it was first reported just over a month ago and our senior management is aware of this issue and its impact. We’ve assigned resources specifically to reproduce, investigate, and fix the problem.
What’s made this problem harder to resolve is it has proved extremely difficult to reproduce it reliably:
- Not every Make user with the Xero app in a live scenario is experiencing the problem (we believe that it’s affecting around 10% of Xero users in Make).
- Where it does occur, it’s not affecting every scenario.
- When it does occur in a scenario, it’s not on every run.
We have now been able to create a scenario that is guaranteed to exhibit the problem on a daily basis and are expecting progress soon.
We are very sorry for all the trouble this has caused you all and we’ll aim to give regular updates on this issue as we work to conclude it.
Thank you very much for bearing with us 