#177 — Replace “refresh connection” with confirmation for disabling integration

Repo: Twill-AI/twill-ai-ui State: closed | Status: done Assignee: raymondehizoba

Created: 2024-12-17 · Updated: 2025-05-07

Description

Caused by Rutter Support ticket filed by Luis.

[Luis] Hi @Rutter Support. We are facing an issue when we disable a connection and enable it again. We perform both operations via the versioned/connections/disable?access_token=... and the versioned/connections/enable?access_token=... APIs. The issue is that, when we try to re-enable the connection, we get error with 405 or 401 status code. I have seen this error might happen if there is a short time between one operation and the other one.

[Rutter support representative, Linda] Yes there would be a bit of lag between when you can re-enable and disable the connection. I see that you are enabling and re-enabling very shortly after one another. I would suggest waiting over an hour before re-enabling the connection. … We actually don’t have the enable/disable endpoints in our docs because we usually don’t recommend customers enable/disable connections. It is really easy to cause data gaps and interrupt the incremental syncs when customers do this. However if customer do end up using it, it should not be done frequently as it takes time for us to fully disable/enable and restart/stop the syncs. This is why you are seeing issues arise when the customer are quickly calling one endpoint right after another.

[Aleksandr] Thank you Linda for details about the inner implementation. We would rework this functionality to “try again” completely on our si

Notes

Add implementation notes, blockers, and context here

Related

Add wikilinks to related people, meetings, or other tickets