Activities Tab

The Activities tab displays the history of all retrieval operations for a specific Salesforce org connection.

Overview

The Activities tab is available within each connection and shows a detailed log of retrieval jobs performed on that org. These jobs include both automatic retrievals (performed in the background by Revvy) and manual retrievals (initiated by clicking the Retrieve button).

Each activity entry helps you track when metadata was fetched, its status, and the duration of the job.

Activity Details

For every retrieval entry, the Activities tab displays:

  • Type: The type of operation (e.g., Retrieve).

  • Status: Indicates whether the job is In Progress, Completed, Aborted, Queued, or encountered an Exception.

  • Date Started: The timestamp of when the job began.

  • Duration: How long the job took to finish.

  • Created By: The system or user that triggered the retrieval.

Logs

Clicking on an activity entry opens a detailed view of the job logs. These logs are especially useful for troubleshooting when a job encounters an error or exception, as they provide step-by-step execution details from the retrieval process.

  • On the left panel, you’ll see job metadata such as Job Status, Created By, Duration, Date Started, and Completed Date.

  • On the right panel, you’ll see the execution logs (e.g., job started, metadata listed, cleanup completed, retrieval finished). This stream shows the real-time steps performed during the retrieval.

Filters

The tab includes filters to help narrow down results:

  • All Types: Filter by job type (currently Retrieve).

  • Status: Filter by job status (In Progress, Completed, Aborted, Exception, Queued).

  • Date Range: Select a custom time range to display activities from a specific period.

Parallel Retrievals

Revvy supports parallel retrievals across orgs. This means that even if you are connected to multiple Salesforce orgs, retrieval jobs run simultaneously in the background — ensuring faster synchronization without manual intervention.

Best Practices

  • Use the Status filter to quickly spot failed or aborted retrievals.

  • Regularly check the Duration column to identify unusually long retrievals that may indicate Salesforce org issues.

  • Review the Created By field to confirm whether a job was triggered by a system process or a user.

Last updated

Was this helpful?