Live updates

Spider keeps the pages you have open up to date while you work. When a colleague adds a trigger, a run finishes, or a process writes a collection item, the page you are looking at shows it, without you clicking Refresh.

What updates by itself

• Lists reload the rows you see when one of them changes, is deleted, or a new one is added.
• A list that grows fast, such as a list of runs, doesn't push new rows in while you read it. It offers them instead: see New rows.
• An item's page, such as a group or an agent, reloads when the item changes.
• A run's page follows the run: its status, and on its Logs tab the node that runs now, with new log lines added at the bottom as they are written. Once you pick a node yourself, the tab stays on it.
• An editor, such as the process designer or an e-mail template, doesn't change what you are typing in. It tells you that the item changed: see Changed elsewhere.

Dashboards are the exception: they refresh on a timer of their own.

New rows

When runs are added to a list of runs while you read it, a Load 1 more button appears in its title bar (or Load 2 more, and so on):

It counts only the new rows that match your search and filters. Click it to show them. The rows you were reading stay where they are until you do.

The same button is on the lists of trigger runs, a collection's items, and an agent's history.

Changed elsewhere

When an item you are editing is changed by someone else, or by a process, a banner at the top of the editor says so: "Delivery confirmation" was changed by someone else. What you typed stays as it is.

• Reload shows the item as it is now. What you have not saved is lost.
• Dismiss hides the banner and keeps what you typed.

The designer is different: everything you do there is saved at once, so Reload loses nothing.

Your own changes never raise the banner, not even ones you made in another browser tab.

When the item you have open is deleted, the banner says "…" was deleted., with a link Back to the list.

Live updates paused

Live updates need a connection to the server, separate from the one that loads pages. When that connection is lost, a tag in the header says Live updates paused:

Spider keeps working while the tag shows, but the pages show what they last loaded. Spider tries to connect again by itself: at first within seconds, then every half minute or so. There is nothing you need to do.

Nothing is lost while the tag shows. When the connection is back, the tag goes away and every open page reloads what it shows. An editor can't know what it missed, so it says "…" may have changed while live updates were paused.:

Click Reload to be sure you see the latest version, or Dismiss to keep what you typed.

When the tag stays for a long time, a firewall or proxy may block the connection. Ask your IT department, or the Helpdesk.

Watching an agent at work

An agent is the computer that runs a process's activities. Its page, in Administration, has a Live tab that shows what the agent's screen shows while it works: Live frames, or the Screenshots its activities take. The tag says ● Live while frames arrive, and Paused when they don't.