Bulk actions and scheduled maintenance
Use a batchable action when the same operation needs to run across several systems. For work inside one PBX, select the users or phones you want to change and use the actions available for that selection.
Fleet actions create a separate result for each target. Open the batch in Run History to see which PBXs succeeded and inspect any failed run before deciding what to do next.
Select instances in the fleet table, or build a target scope from instances, groups and tags.
The available actions follow the selection and your permissions. Confirmation appears when the action requires it.
One row per PBX in Run History; open a failed run to read the error and its parameters.
A failed leg keeps its own record: the target, the parameters that were sent, the error returned by the PBX and the batch it belonged to. Nothing is retried silently.
The selection stays within that instance. Options and results are reported per object.
Users
Select the extensions that need an update, then use a specific operation such as Set Outbound Caller ID or Change Department. The PBX name stays in view; the operation targets those users and nothing else.
Usages
Show Usages, in a user's row menu, lists what points at that extension on the PBX: the queues where it is an agent or a manager, the ring groups and departments it belongs to, IVR menu keys and timeout or invalid-key forwards, break, holiday and out-of-office routes, inbound and outbound rules, and the phones assigned to it.
Phones
Select provisioned phones and open Edit IP Phone Options. Options are grouped by the phones’ templates, and results are reported per phone when some updates fail.
When a handset refuses the update, it is listed with its reason and the other phones keep their new options. Nothing is rolled back behind your back, and nothing is reported as done that was not.
Choose the targets, recurrence and time zone, then add actions in the order they should run. Control rolling batches and maintenance-window behaviour, and review the schedule’s run history.
Each run records its stages and targets. Within a stage, one failing target does not stop the others; a stage that does not fully succeed stops the stages after it. Skipped runs keep their reason.
Backups and updates
Run backups, export backup files to workspace storage and configure the backup or update settings SYNOP•SYS supports. Schedule those operations and inspect their results; backup exports count against the workspace’s storage allowance.
Tell us in your request; it is usually the first thing we help set up.
