There is a specific way Instagram automation fails that catches almost everyone once.
Everything works. Comments trigger DMs, rewards go out, the campaign converts. Then, some weeks later, it stops. No error, no email, no warning. Your dashboard still shows a green Connected badge, so you assume the problem is your content, your keyword, or the algorithm.
It is usually none of those. Your access token expired, and nothing told you.
What actually expires
When you connect an Instagram account to any automation tool, you are not handing over your password. You are approving an access token, which is a temporary credential that lets the tool act on your behalf within the permissions you granted.
Meta deliberately makes these temporary. A long-lived Instagram token is good for roughly 60 days. Tools can refresh it before it lapses, which is why the practical lifetime people report tends to land somewhere between 60 and 90 days rather than exactly 60.
The important detail is that refreshing only works while the token is still valid. It is a renewal, not a resurrection. Once the window closes, no amount of background retrying will bring it back. Someone has to go and approve the connection again.
This is not a flaw. A credential that never expired would be a serious security problem, especially one that can message your audience. But it does mean recurring maintenance that most creators are never warned about.
Why the dashboard lies
Here is the part that turns a small maintenance task into a confusing outage.
Most tools write a status value when you first connect, something like Connected, and then never check it again. The label is a stored record of what happened once, not a live test of whether the credential still works. Unless something in the system actively re-validates on a schedule, that badge stays green forever.
We can be specific because we found it on our own infrastructure. One of our internal Instagram accounts was carrying a token that expired on the first of the month. Weeks later, the database row for that account still read Connected, with webhookActive set to true. Nothing in the interface suggested a problem. The automation for that account had simply been dead the whole time.
If it happens to the people building the tool, it is happening to creators using every tool in this category. The lesson is not that one product is careless. It is that a status label is only as trustworthy as the last time something verified it, and you cannot tell by looking.
How to tell a dead token from a permissions problem
These two failures look identical from the outside, and the fixes are different, so it is worth learning to separate them. The test is whether your tool sees the comments.
| What you observe | Likely cause | Fix |
|---|---|---|
| Comments are logged, no DMs go out | A message permission is off | Turn on Allow Access to Messages in Connected Tools |
| Nothing registers at all, including comments | Token expired | Reconnect the account and re-approve permissions |
| Worked, then stopped at roughly the two-month mark | Token expired | Reconnect, then set a reminder |
| Fails only for some recipients | The 24-hour messaging window | Not a credential problem |
| Stopped on one post only | The post was archived or re-uploaded | Re-point the campaign |
If comments are arriving in your tool's activity log, the credential is doing its job and you should look at the message permission instead. Our full breakdown of comment-to-DM failures walks through the rest in order of likelihood.
The maintenance habit that actually works
Since you will not reliably be told, the practical answer is to make expiry something you check rather than something you wait for.
Reconnect roughly every two months, before anything breaks. It takes under a minute, it is safe to do while the token is still valid, and a reconnect while things are working is much less stressful than debugging silence.
Reconnect before anything that matters. If you are launching a product, running a giveaway, or posting something you expect to perform, reconnect first. The worst time to discover a dead token is during the one Reel that took off.
Treat quiet as a signal. If a campaign that was converting goes flat, check the credential before rewriting your hook. Content is the usual suspect and often innocent.
Note the date, not just the status. If your tool shows an expiry date anywhere, that number is far more useful than the word Connected. A date in the past is unambiguous in a way a status label is not.
What to ask a tool before you commit
If you are choosing between automation tools, this is a genuinely useful question and almost nobody asks it: how do you detect an expired token, and how do you tell me?
Good answers sound like scheduled re-validation, a real expiry date shown in the interface, or an email when the credential is close to lapsing. A weaker answer is a status field written once at connection time. The difference does not show up in a feature comparison table, but it decides whether your automation fails for an hour or for three weeks before you notice.
It is also worth asking whether reconnecting preserves your campaigns and participant history. In most tools it does, because the credential is stored separately from campaign data. In a few, disconnecting is destructive, and that is much better to know in advance than to find out mid-campaign.
The short version
Instagram tokens expire every 60 to 90 days by design, refresh only works while they are still alive, and the Connected badge in your dashboard is very often a stored value rather than a live check. Nobody is likely to tell you when it lapses.
Reconnect every couple of months as routine maintenance, reconnect before anything you care about, and when a working campaign goes unexpectedly quiet, check the credential before you blame your content.
UnlockDM stores an explicit expiry date for every connected account, which is the number worth checking. Reconnecting from Settings refreshes the credential and leaves your campaigns, participants, and history untouched.
