@Michaela Unfortunately, it appears this issue is still persisting. Just woke up to see a couple dozen error emails about failed scenarios being deactivated.
Happy to work with Make to provide additional data as needed to get this solved.
@Michaela Unfortunately, it appears this issue is still persisting. Just woke up to see a couple dozen error emails about failed scenarios being deactivated.
Happy to work with Make to provide additional data as needed to get this solved.
Hello everybody @here
First of all, thank you very much for your updates. They are greatly appreciated
We understand the frustration caused by this ongoing issue, and our engineering team is actively working on it as a top priority. Unfortunately, a recent fix didn’t fully address the problem, so we’re intensively testing real-world connection scenarios in our development environment to pinpoint the underlying cause.
While we can now consistently replicate the issue in isolation, we cannot provide an exact resolution timeline just yet. We will make sure to update you as soon as we have additional information on a resolution time.
We genuinely apologize for the ongoing inconvenience and frustration this situation has caused. Your patience and understanding are highly valued.
Hello Michaela,
I drive a fair chunk of my business from doing Xero automations, so this is causing a major impact on my relationship with clients. To constantly contact (think senior management, CEOs) to log back in and constantly reauthorize the connection and get flooded with error messages a couple of days later and have to re-do the process is incredibly frustrating.
I have my own app on the Xero app store, so I understand the workings of the Xero API quite well, so if your developers need to brainstorm a resolution with someone proficient in Xero, please ask them to reach out to me.
Hello @D-EFFCON,
first of all, let me say how sorry for all the trouble and inconvenience caused by the ongoing issue. I understand that this is incredibly frustrating but please know that our team is working to thoroughly investigate and resolve this matter.
Also, thank you so much for offering to collaborate with the dev team. We truly value that and we’ll make sure to keep it in mind
thanks @michaela for keeping us updated.
It’s even WORSE on my end. it was OK for a few days last week but now its daily re-authorization required again…
Thanks Michaela.
Just an FYI; it appears to have happened again. I believe both this time and last time that I’ve commented immediately after I discovered the issue - so it appears that it lasted about 7 days before the connection failed again.
Thank you for communicating about all this -
On the off chance there’s not a solution any time soon - based on what the Dev team knows about the issue is there any way to set up a scenario to minimise these occurrences?
Also might be helpful for us to provide a description of what the issue is exactly, so we can try to work around it?
Any best practices to follow anything, this keeps tripping us up, very frustrating
Noting as it doesn’t seem to be noted anywhere here that when I check the connection - the error there reads:
“The request failed due to failure of a previous request.”
So it seems once it breaks for whatever reason, the module or Xero seem to reject any subsequent requests -
If you can fix that second problem - I think we can work around the first (whatever it is) with a break error handler - lots of modules dont work sometimes but where this is unique is that it stays broken
Edit -
Also just looked into this a little more - I have no idea what other people are experiencing but the recent run of errors had a definite and predictable pattern
Last 3 initial errors:
29 Sept 2023, 8:00:14 am
22 Sept 2023, 8:30:02 am
15 Sept 2023, 8:30:02 am
Note the second and third last errors are 7 days apart to the second!
Anyway I think I have my fix as our operation is fairly small -
Every Friday 8AM - Check Xero connection Check again at 9:00 and later in the day
Can’t be a coincidence … right?
That’s a great idea Michael. Am error trap or something so my inbox doesn’t get filled with errors.
Ian
I believe before Make runs a scenario, it checks that all connections are valid.
So I feel the flaw here is either within the
-API call check that’s happening to see if the connection with Xero is valid
-The token reauthorisation is not being properly regenerated/saved.
Or it could be both.
@Michaela Just for the record, I’m not intending to direct my frustration at you personally, it just so happens that unfortunately as the Make community spokesperson it, I need Make to take this seriously and so it seems so far that the only avenue to seeing any progress is via here, and thus via you.
This issue has been present for many months, and formally presented in Jul 20 (as can be seen at the start of this thread). We are now in October, with no real transparency as to
a) what the issue encountered is
b) how many actual engineers have been assigned to this issue
c) what the battle plan for said issue is
d) what fixes have been applied so far and why it failed to fully solve the problem
So yea, I hope you can understand why I’m being more vocal on getting this solved ASAP.
Hello @here
First of all, thank you all very much for sharing all the extra information and context with us. This is greatly valuable and appreciated.
I’ve shared this thread with our dedicated development team who are actively working to identify the root cause and implement a solution. Your voices are not going unheard and we are taking this matter seriously.
I understand the challenges and frustration this issue has caused and I sincerely apologize for the extended timeline in resolving it. Unfortunately, identifying the underlying problem is taking longer than anticipated. However, please know that resolving this matter is one of our top priorities.
I will continue to keep you updated here as soon as I learn anything new about this issue.
Once again, your collaboration, understanding, and patience are deeply appreciated
Hello everyone @here
I just want to let you know that we rolled out a fix for our Xero app. Could you please take a moment to try reauthorizing and keep us posted on the status?
Once again, I would like to thank you for your understanding and patience throughout this process. We really value your continuous involvement and all the extra context you have been bringing us.
Fingers crossed! Has this been rolled out to all instances at once, or staggered like the last fix was?
Hi I am sorry to report that I had a recurrence of the error today. When it happened earlier in the week when it happened i went into Xero and related the connect and made a new one and then went into each Scenario and updated it to the new connection.
I had over 30- messages, and still counting.
thanks, Ian
Hello @Ian_Kerry I am so very sorry to hear that the issue still persists.
However, thank you very much for the update, your ongoing communication is greatly appreciated.
If you haven’t already done so, could you please open a ticket with our support team? Doing so would be incredibly helpful as it allows our support team to investigate the specific scenarios affected. By doing so, they can better trace the issues and provide precise technical insights to our development team.
Once again, thank you ever so much for your continued support throughout this issue.
Your patience and understanding are greatly appreciated
@Michaela - is it possible that this is now fixed? I haven’t received an error for 10 days.
Probably shouldn’t be tempting fate…
How is everyone else doing?
Ta
Ian
Hello @Ian_Kerry thank you very much for jumping in with an update from your end
It’s great to hear that you’ve gone 10 days without an error. I am really hoping that we are not jinxing this and that all will continue to run smoothly from now on.
To answer your question:
The team deployed a fix to this ca 4 weeks ago and they’re refining things further based on the valuable feedback and collaboration we receive from our users. Your input has been instrumental
Hi Michaela,
At the same time I received the notification of your email, I also received an email saying a scenario had stopped because of the usual Xero error.
I only had it once though, for one scenario.
Just so you know I did delete my xero connection, renamed it, and then re authorised, and went into every scenario to point it to the new connection.
I am only telling you this in case it helps. I can cope with one error every 10 days!
Thanks
Ian
Hello again Ian
The timing of life, isn’t it just so typical? It seems we might have jinxed things after all.
Once again, thank you so much for continuously coming back to this thread and for keeping us informed on how things are going with your connection.
Just to provide some context from our end, we’ve deployed a fix to the root cause of the problem. Any remaining issues could be specific to individual accounts. For that reason, we encourage anyone who’s still facing these issues to open a support ticket with us. I see that you’ve done that and that you’re chatting with our team. Please continue doing so, I’m sure we’ll eventually manage to solve this.
Also, let me say that your positivity and open-mindedness regarding this issue are truly amazing. Thank you so much for your approach and for your patience
@Ian_Kerry I’ve not had any errors for over 2 weeks which is great! (Touch wood).
I also made a new connection and updated scenarios to be on the safe side.
So far so good!