​
Overview

Simnet has two activity surfaces and they answer different questions.

​
Why jobs exist

Almost nothing in Simnet completes instantly. Creating a VM, building a VPC, attaching a volume — each is submitted to the platform and carried out in the background. A job is that unit of background work. This is the single most important thing to internalize about the console: when an action returns without an error, it has been accepted, not completed.

​
Job statuses

The Jobs screen shows four badges:
The platform reports more granular states internally, which the screen collapses into these four. One consequence is worth knowing: a job the backend calls PENDING is displayed as Running, because the platform already treats it as in flight. Only genuinely queued work shows as Pending.

​
Waiting on a single action

When you submit something from a dialog, the console follows that one job directly and reports the outcome to you, rather than making you go find it in a list. Two behaviors are worth knowing:
  • A momentary inability to read the job is not a failure. The console retries rather than telling you your VM creation broke.
  • “Timed out” does not mean “failed.” The console gives up watching after about two minutes. The operation is still running on the platform. Check Monitor → Jobs for the real outcome.
Don’t retry an action that appears to have timed out until you’ve confirmed the job’s status. Retrying a create that actually succeeded leaves you with two resources and consumes double the quota.

​
Why events exist

An event is a durable audit record: something happened to a resource, at a time, at a severity, attributed to a user. Events aren’t a live view of work in progress — they’re the history you consult afterwards.

​
Event levels

Three levels, and the dashboard’s health banner is driven by the top two:

​
Which one do I want?

Check Monitor → Jobs, filtered to the last hour. A Running job means it’s still coming. A Failed job shows the error underneath the job name.
Check Monitor → Events and filter to the resource. Events retain the history; jobs only cover operations the platform ran on your behalf.
Start at the dashboard’s health banner, which summarizes errors and warnings for your selected timeframe, then use View all → to open the full event list.
Events record the acting user. For an account-wide view organized around people rather than resources, use Organization → Audit Log.

Monitor

The Events and Jobs screens, with their columns and filters.

Dashboard

The health banner and the Recent Activity panel.