








































































































.webp)





















OSIsoft PI System (now AVEVA PI) is the industry-standard real-time data infrastructure for industrial operations, collecting and analyzing time-series data from plant assets.
Have any questions? We’re here to help You
Yes, you can trigger syncs manually through both the API and the Makini dashboard. The API provides endpoints to initiate syncs for specific entities (purchase orders, work orders, etc.) on a given connection. Manual syncs are useful when you need immediate data updates outside the regular schedule, when onboarding new customers, or when recovering from sync failures. Manual syncs follow the same incremental logic as scheduled syncs, retrieving only changed records since the last successful sync. You can also trigger full re-syncs that ignore the last sync timestamp and retrieve all records within the configured historical period.
Makini sends webhooks for several event types: sync completion (successful or failed), connection authentication required (when credentials need renewal), connection status changes (online/offline), and system errors requiring attention. Each webhook payload includes the event type, timestamp, connection ID, and event-specific details like error messages or affected entities. You can configure which events trigger webhooks on a per-connection basis. For workflow-based integrations using Makini Flows, you can also set up custom webhooks triggered by specific conditions in your business logic, providing granular control over real-time notifications.
The RATE_LIMIT_EXCEEDED error indicates you've exceeded the API rate limit for the connection or account. Rate limits are typically set per connection and per time window (usually per minute). When you hit a rate limit, the response includes a Retry-After header indicating when you can retry the request. Implement exponential backoff in your retry logic to avoid immediately hitting the limit again. If you consistently hit rate limits, review your API usage patterns—you may be making unnecessary requests, polling too frequently, or could benefit from webhook-based synchronization. For legitimate high-volume needs, contact us to discuss increasing your rate limits.
Yes, through a combination of sandbox environments, test data, and Makini Flows. For testing different data states, use sandbox connections with predefined test scenarios. For testing system behavior like delays, errors, or specific responses, you can build test workflows in Makini Flows that simulate various scenarios. For testing with actual systems, set up dedicated test instances of your target systems. During implementation, we work with you to identify critical test scenarios and ensure your testing environment supports them. For specific edge cases or unusual system configurations, we can help create custom test scenarios.
