Core web and Cloud
Account access, Cloud metadata and ordinary file operations depend on the application and primary storage services.
Capability
Service availability
Understand the operational dependencies that affect Cloud, transformations, email, embedded access and external providers.
Overview
Availability is separated by capability so a provider or background worker issue does not imply that every Apification function is unavailable.
Features
What Service availability can do
Background processing
Transformations, imports and media renders require active queues and their corresponding processing binaries.
Email and OTP
Invitations, notifications and one-time passwords require the configured mail delivery service.
External providers
Office editing, storage imports, authentication and AI can be affected by the selected third party.
Degraded-operation guidance
Preserve job status and retry only when the operation supports a safe retry path.
Incident contact
Report the affected account, service, approximate time and operation identifier without sending secrets.
Frequently asked questions
Questions about Service availability
Not yet. It documents capability boundaries and the support information needed during an incident.
API and account workflows expose retry only for eligible failed or cancelled jobs.
Include time, affected capability, account context and safe job or service identifiers, but never passwords or API secrets.