Activity Logs

Activity Logs

Action Logs is the record of everything Quickly has done in your workspace. It is the audit trail for compliance, and the first place to look when an answer was not what you expected.

What a Log Entry Contains

Every request becomes a task, and every task holds the tool calls made while handling it. For each call you see:

• The tool that ran, and the integration it belongs to
• Whether it succeeded, failed, or is still pending
• How long it took
• A link to whatever it produced, such as the created issue or page
• The policy decision that allowed it

Policy Decisions

Each tool call is labelled with why it was permitted or stopped:

• Auto — allowed by the current autonomy mode and ran without asking
• Needs approval — paused for a human to approve before running
• Blocked (Safety) — refused by the safety rules
• Blocked (Member) — refused because the Member role is restricted from this tool
• Blocked (Admin) — refused by an Admin's explicit tool policy

This is what makes the logs useful for tuning autonomy: if a tool your team trusts is constantly showing Needs approval, that is the case for an AUTO override. If something is showing Blocked, the label tells you which rule to change.

Filtering

The filter bar narrows the view by:

• Search across task titles and message content
• Task status — Open, Closed, or Abandoned
• Outcome — Succeeded, Failed, or Pending
• User who made the request
• Tool that was called
• Agent that handled it
• Date range

Filters combine, so "failed Jira calls by one person last week" is a single view rather than a manual scan.

Exporting

Export downloads the current view as CSV, named for the date it was taken. Each row carries the task ID, task status, credit status and credits charged, the timestamp, the message role, the tool name, the event status, the duration in milliseconds, and the external ID of anything created. That last column is what lets an auditor match a Quickly log line to a record in the destination system.

Investigating a Failure

Open the task to see the full sequence. A failed call carries the error the external service returned, which usually distinguishes the three common causes immediately: an expired OAuth token, insufficient permissions in the external tool, or an invalid field such as a workflow transition the target project does not allow.

For an expired token, the owner of that connection reconnects it under Settings > Integrations > Connectors. For a permissions error, the fix is in the external tool, not in Quickly.

Credits

Because each task records the credits it consumed, the logs double as the detail behind the usage figure in Settings > Billing & Usage. Sorting a period's tasks by credits charged is the quickest way to find which automation is costing the most.

Working Through the Logs

Three routines cover most of what teams use Action Logs for.

How to audit a task

1. Open Action Logs.
2. Find the task by user, status, date, or tool.
3. Review messages, tool calls, approvals, and final output.

How to investigate a failed task

1. Open the failed task.
2. Read the tool summaries and visible messages around the failure.
3. Check whether the cause was missing auth, bad parameters, policy block, or provider error.

How to review browser evidence

1. Open the task detail.
2. Find browser recordings, screenshots, or session links when present.
3. Use them to confirm what page state Quickly saw.

Good to Know

• Use Action Logs when reconciling user reports with actual tool execution.