Use Activity Log and contact support

What this guide is for

Activity Log helps you reconstruct what happened across the workstation. Use it when an import, Study, connection, or other action needs investigation, or when you need to prepare a useful support request.

Activity is an event history. It does not replace the page that owns the underlying object. Job state belongs in Jobs, a Study outcome belongs in Results, and a Live order must be checked against its order, fill, and broker records.

Find the event you need

Open Activity Log, then narrow the list by time, severity, owning area, or event type. Start with the approximate time of the action and work outward.

A useful entry can show:

• when the event occurred;
• which part of Arizmic produced it;
• the object type and a safe identifier;
• the resulting state or severity;
• a bounded message or error detail; and
• a route back to the owning page when one is available.

Read related entries in order. One line may record that a request was accepted, another that work started, and a later line that it completed or failed.

Distinguish Activity from Jobs

Use the header for a quick view of active work and System & Jobs -> Jobs for the complete queue, progress, attempts, and controls. Use Activity Log when you need the wider sequence around that Job, such as the action that created it or a connection change that happened nearby.

Progress and event timestamps help diagnose a workflow, but they do not prove that an output is complete. Return to the owning page and confirm the object is listed as available before using it.

Prepare a support request

Include only the information needed to reproduce the problem:

1. the Arizmic version and operating system;
2. the page, tab, and action you used;
3. the affected object type and safe identifier;
4. the approximate time and timezone;
5. the Job ID or Activity event reference;
6. the exact visible error message; and
7. whether the problem remains after a launcher-managed restart.

If support asks for diagnostics, create them from System & Jobs -> System Settings. Review the file before sharing it.

Never send API keys, broker credentials, license keys, account numbers, private model prompts, unrestricted file paths, full Datasets, or proprietary Strategy source in an ordinary support email.

Clear records carefully

Clearing eligible Activity entries is maintenance, not data deletion. Review the selected scope before confirming. Clearing Activity must not be treated as a way to remove Datasets, Prepared Data, Studies, Results, or Live records.

Keep relevant events until a failure, billing question, provider dispute, or support case is resolved.