System Status

Macro Handler status and incident communication

This page gives users a clear status reference for which surfaces are monitored, which channels are used during incidents, and where operational updates are published.

Identity and access

Google sign-in, premium entitlement, badge rights, and community access are monitored first by client smoke checks and then by server callable controls.

Automation runtime

Critical regressions in accessibility, overlay, capture, and runtime flows are monitored through release gates and smoke tests.

Community and sharing

Moderation, rate limiting, and backend contract signals are tracked across forum, public macro, and direct-share flows.

Public update channels

For release-level changes and permanent fixes, use Changelog.
For user assistance, account, moderation, and support requests, use Support.
For community-facing announcements and user-impact updates, use Forum.
To follow planned hardening and platform priorities, use Roadmap.

What should you expect during an incident?

If critical flows such as identity, premium, or sharing are affected, protected backend controls and release smoke evidence are reviewed first.
When a user-impacting issue is permanently fixed, the changelog and the relevant support/forum surface are updated.
For legal or account-security matters, the contact channel is support@macrohandler.com.