Auto-post to LinkedIn. Retries properly. Logs everything.
The Logs screen holds 10 rows: successes carrying post URNs, a 429 that backed off and succeeded on the retry, and a 401 parked as a permanent failure rather than retried. Every one of them was written by the plugin’s own code.
What to look at
Logins
- Admin, read-only —
viewer.demo / ibuilder-demo-viewer(every admin screen opens; saving is refused)
What this demo does not show
This demo is not connected to LinkedIn. It is connected to a local stub that answers the endpoints the plugin calls, with a scripted sequence of real HTTP responses — several 201s, one 429 with a Retry-After, one 401 with LinkedIn’s REVOKED_ACCESS_TOKEN body. The retry decisions, the backoff, the parking of the 401 and every row in the log are the plugin’s own behaviour; only the choice of which response came back is ours. The master switch and manual publishing are both off, so nothing on this site can post anywhere.
