Engineering
When a connector login breaks: finish once, pause, wake—never bypass
A dead connector keeps failing every hour and burns usage quietly.
What hurt
Paulo Pierrondi (@paulopierrondi) fences connector failures: first failure finishes what it can and notes it; same failure again pauses that routine instead of retrying blind; then wakes you with what needs reconnecting; never goes around the broken login through a browser side door. A paused routine beats a quiet hourly fail. Not affiliated with xAI.
What to install or create
Note once → pause on repeat → wake for reconnect → ban browser bypass.
Bots
Any connector bot
Pauses on repeat login failure and wakes you; no side doors.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/paulopierrondi/status/2112703831544824063 (credit @paulopierrondi).
- 2Paste the four rules into each bot that uses connectors (or your chief's standing rules).
- 3On first failure: finish what you can, note it in the result.
- 4On repeat failure: pause that routine; wake you with what needs reconnecting.
- 5Never allow a browser workaround around a broken connector login.
Approval fence
You reconnect the login; the bot only pauses and reports.
What to tweak
Steal the four-step fence; put it in every bot that uses connectors.
Source
Paulo Pierrondi @paulopierrondi · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.