Durable task history
EPAdmin Server Logs → Tasks and Customer Operation history show authorized durable jobs. Lists use cursor pagination; a task detail and its events preserve the operation's progress. The source distinguishes queued/running, succeeded, failed, cancelled, compensated and compensation-failed outcomes. Keep the original operation ID and inspect actual resource/service state before retrying an interrupted write.
Cancellation uses POST /v1/operations/{id}/cancel with an empty body. It requests cancellation; it does not erase already applied effects or promise instant termination. Generic operation submission accepts only the supported typed marker contract; hosting lifecycle changes use their dedicated endpoints.
Choose the correct log
Server service, security and system log categories require their own read grants. Website raw/error logs remain resource/account-scoped. Application logs and content use application IDs and bounded offsets/limits. Web Server Logs does not imply a full visitor analytics/AWStats suite: those Customer menu features are unavailable. Log retention, supported stream and byte bounds come from the installed contract, not arbitrary server file paths.
Notifications and security activity
Notifications include kind/state/severity/code/event/observation time and read state. Mark read sends the exact notification sequence; changed records are refreshed. Read-only Customer View cannot mark them. Security/login activity is separately grant-filtered; a notification is a pointer to evidence, not a grant to change the underlying resource.
Operational alerts distinguish expected security, website and service guidance. A rejected/blocked action is not resolved by suppressing the alert. Email delivery depends on the independently configured notification SMTP and verified identity-owned address.
Support summary
An authorized administrator can collect GET /v1/server/support-bundle. The UI validates the bounded emailaoribit-support-summary-v1 format and offers a JSON summary download. This is not a whole-server archive, raw configuration dump or interactive root support session. Review it before sharing and use the private support channel.
Safe issue report
Include exact release, role/workspace, sanitized operation/correlation reference, action, timestamp and observed versus expected result. Exclude passwords, API tokens, session cookies, recovery codes, private keys, mailbox contents and database dumps. Unknown/private log paths must stay denied. On storage/agent unavailability, preserve failure history and inspect the owned service boundary; do not delete journals to make the UI green.