What is the Post Statistics view in Onimator? Post Statistics is one of the specific reporting views inside OniHelper Suite’s Post Monitor tool, showing per-post status across every scheduled post on the selected device or across the entire fleet — which posts succeeded in publishing, which failed, which are still pending, and the specific timing and metadata associated with each. It is the primary diagnostic surface operators use to understand publishing operations at fleet scale, and it is the specific view that surfaces the operational data Post Rescheduling and Post Monitor’s other recovery workflows operate against. Without Post Statistics, operators would have no unified view of publishing outcomes across the fleet — every post’s outcome would need to be verified per-account, which becomes operationally impractical at any scale beyond a handful of accounts.
What Post Statistics Shows
The view displays a table of every scheduled post on the selected device (or across the fleet if All Devices was selected in the Home sub-sub-tab), with columns exposing the specific metadata operators need to understand each post’s status.
Typical columns include the account username the post belongs to, the specific media file the post references, the scheduled publish time, the actual publish time (populated for succeeded posts, blank for pending or failed), the current status (Succeeded, Failed, Pending, or intermediate states), and any error details for failed posts. The specific error detail helps operators distinguish between different failure categories — session interruptions, network issues, per-account restrictions, content validation errors — which drives different recovery responses.
The view populates only after the operator explicitly loads it. Opening the Post Statistics sub-sub-tab without first clicking Load Post Statistics on the Home sub-sub-tab produces the specific empty-view state with a message directing operators to load from Home first. This design pattern reflects that loading statistics across large fleets can be expensive, and the explicit load action prevents accidental heavy queries when the operator switches between sub-sub-tabs.
How to Load It
The specific workflow to populate Post Statistics: open Post Monitor, navigate to the Home sub-sub-tab, point the Bot Path field at the correct installation (Onimator Bot Path for the main install, or the specific Threads Bot Path or TikTok Bot Path for platform-specific installations), select the device to report on (or All Devices for fleet-wide statistics), and click Load Post Statistics. The load action queries the installation’s stored post data and populates the Post Statistics view with current values.
The specific data loaded reflects the state at the moment of the load action, not live-updating state. Operators wanting to see changes after new posts have been dispatched need to trigger a fresh load rather than expecting the view to update automatically. This design pattern prevents the specific case where operators believe they’re looking at current state when they’re actually looking at a snapshot from a prior load.
The Failed/Pending/Succeeded Categorization
The specific status categorization exposed in Post Statistics drives most of the recovery workflows Post Monitor supports.
Succeeded posts represent the successful publishing outcomes — content that made it to the platform and now lives in the account’s feed. These posts require no further operator action; they’re logged for reference but don’t drive recovery workflows.
Failed posts represent the specific case where the automation attempted to publish but the publish operation failed for some specific reason. These posts feed the recovery workflows — Post Rescheduling for the requeue-and-try-again path, Delete Failed Posts for the give-up-and-clean-up path, Export Failed Posts for offline analysis before deciding which recovery path to take.
Pending posts represent posts that haven’t reached their scheduled publish window yet — they’re waiting in the queue for their scheduled time. These posts don’t require recovery action; they’ll process normally when their window arrives. Post Statistics surfaces them primarily for verification (operators confirming that expected posts are queued) rather than for recovery.
Why Post Statistics Matters
The specific value Post Statistics delivers is that it converts publishing operations from opaque to observable. Without it, operators running scheduled posting at fleet scale have no unified way to know whether the publishing operation is working — they see individual posts appearing in feeds when they happen to check, but they don’t see the aggregate pattern of what succeeded, what failed, and what’s still pending across the whole fleet.
Post Statistics surfaces this aggregate pattern in one view. Operators can see, at a glance, that specific devices are producing higher failure rates than others (pointing to device-specific issues), that specific accounts are failing consistently (pointing to per-account restrictions), or that specific time windows produced correlated failures across multiple accounts (pointing to network or platform issues during those windows). The specific diagnostic patterns Post Statistics reveals drive the operator’s response — different failure categories require different recovery strategies.
At fleet scale, the specific alternative — verifying each post’s outcome per-account through platform interface inspection — is impractical. Post Statistics is what makes fleet-scale posting operations debuggable rather than opaque.
How Post Statistics Feeds Recovery Workflows
Post Statistics is the specific data source Post Monitor’s recovery actions operate against. When operators click Reschedule Failed Posts (single device) or Reschedule Failed Posts (All Devices), the action operates on the specific set of failed posts Post Statistics identified during the most recent Load. When operators click Delete Failed Posts, the deletion targets the same set. When operators click Export Failed Posts, the export dumps the same failed-post data to CSV for offline analysis.
The specific implication is that the accuracy of Post Statistics — whether it reflects current state or a stale snapshot — matters for recovery workflow correctness. Operators who trigger recovery actions against stale Post Statistics data can produce unexpected outcomes if the actual state has changed since the last Load (for example, if posts that were pending have since succeeded or failed). Well-configured operator workflows reload Post Statistics before triggering recovery actions to ensure the actions operate on current data.
Where Post Statistics Fits in Post Monitor
Post Statistics is one of Post Monitor’s three view sub-sub-tabs, alongside Share Statistics (which tracks post-publish engagement rather than publish outcomes) and File Mapping (which maps posts to their specific media files). All three views populate on demand from the Home sub-sub-tab, and each serves a specific diagnostic purpose within the broader Post Monitor workflow.
The specific division of labor between the three views reflects that different diagnostic questions require different data. Post Statistics answers “which posts succeeded or failed to publish?” Share Statistics answers “how are the successful posts performing after publish?” File Mapping answers “which specific media files are attached to which specific scheduled posts?” Each view surfaces one dimension of the specific publishing operation without overloading any single view with data that doesn’t belong to its diagnostic focus.
Why It Matters for Automation
Post Statistics is the specific reporting surface that makes fleet-scale posting operations debuggable rather than opaque. Without it, operators running scheduled posting across many accounts would have no unified way to identify failure patterns, verify pending posts, or drive recovery workflows. With it, publishing operations become observable at the fleet level, and the specific data operators need for both routine monitoring and failure recovery lives in one place. For operations running Post Scheduler at any meaningful scale, Post Statistics is one of the specific views operators check regularly — routine fleet-health reviews typically include Post Statistics loads to verify that publishing outcomes match operator expectations.
Related Terms
- Post Monitor — The OniHelper Suite tool Post Statistics lives inside as one of its diagnostic view sub-sub-tabs
- Post Rescheduling — The specific recovery workflow that operates against failed posts Post Statistics identifies
- Post Scheduler — The tool that produces the scheduled posts Post Statistics later reports outcomes for