








































































































.webp)





















Swisslog provides intralogistics automation and warehouse management software including SynQ WMS for orchestrating robotics, AS/RS, and conveyor systems.
Have any questions? We’re here to help You
Makini is SOC 2 Type 2 compliant and undergoes penetration testing twice annually. We use industry-standard encryption protocols including TLS 1.2+ for data in transit and AES-256 for data at rest. Customer credentials are encrypted using secure key management practices. Our infrastructure follows security best practices including network segmentation, access controls, and regular security audits. For highly regulated industries or customers with strict compliance requirements, we offer self-hosted deployment options that keep all data within your infrastructure. We've successfully met security requirements for enterprises including financial institutions and government contractors.
Data synchronization frequency is configurable based on your requirements. For real-time needs, Makini supports webhook-based synchronization where changes trigger immediate updates. For scheduled syncing, common intervals range from every 15 minutes to daily, depending on data volume and business requirements. The initial sync after connecting a system retrieves historical data based on your configuration—typically 30-90 days of historical records. Subsequent syncs are incremental, retrieving only records created or modified since the last sync. Sync frequency doesn't affect pricing. You can also trigger manual syncs on-demand via API when needed for specific workflows.
Makini provides a /sync-status API endpoint that returns the current synchronization state for a connection. The response includes the last successful sync timestamp, sync status (in progress, completed, failed), any error messages, and the next scheduled sync time. You can query this endpoint to monitor sync health and detect issues. For workflow-based syncs using Makini Flows, each workflow execution is logged with detailed status information including start time, completion time, success/failure status, and any errors encountered. The Makini dashboard also provides visual sync status monitoring across all connections.
Connection-specific errors often relate to system configuration, permissions, or connectivity issues. Common scenarios include: the system is offline or unreachable, credentials have expired, API rate limits on the source system, or permission changes in the source system. Use the connection status endpoint to check connection health before making API calls. Implement circuit breaker patterns—if a connection repeatedly fails, temporarily stop making requests to avoid cascading failures. Log connection-specific errors separately to identify problematic connections. When errors occur, check if the issue affects all operations or specific entity types, which helps narrow down permission or configuration issues. For on-premises systems, verify network connectivity and firewall rules. Contact support if connection errors persist, providing the connection ID and affected operations.
