When nothing is running
Automation is stopped and it is not obvious why. It is almost always one of these six.
At a glance
- The 'automation suspended' banner at the top — deliberately not dismissable: it names the reason and carries the button that fixes it
- 'Automation paused' — you paused it yourself from the system tray menu. Unpause it from there
- 'Automation suspended: documents to accept' — until you accept the terms, Booost acts towards nobody. No grace period: this is a choice, not a fault
- 'Automation suspended: subscription inactive' — the check asked the server and got a no
- 'Automation suspended: subscription unverifiable' — the service is not answering. The app keeps working for 24 hours from the last successful check, then stops
- 'Automation suspended: you are not signed in to Booost' — sign back in and the queue resumes
How it works
The two subscription messages are worth telling apart. 'Subscription inactive' means the server answered, and the answer was no: the block is immediate and has no grace period, because a definitive answer needs none. 'Subscription unverifiable' means the server did not answer at all — and then you get 24 hours of autonomy from the last successful check, because a dropped connection is not a lapsed subscription.
If you press 'Re-check' and nothing changes, the request did go out: it means the server keeps answering that no subscription is active. At that point the problem is not in the app and retrying will not help — check your payment status from your Booost account, or write to us.
Two more things stop everything without going through that banner: an expired LinkedIn session (log in again from the Browser tab — the account stays the same) and a tripped circuit breaker, shown on the Home page under safety. The breaker opens when LinkedIn shows a risk signal and closes again on its own: forcing it open early is the fastest way to get suspended.
If automation is running but nothing gets published, look in Content: the posts are probably sitting there waiting for you to confirm them, which is the default behaviour.