Finding Activity and Troubleshooting Records

Key Takeaways

  • Use Search Events for audit events and Account Activity for detailed source operations.

  • Check source aggregation history, deployment detail, or workflow executions when investigating that specific work.

  • An approval decision, a manual task and a completed native change produce different evidence.

  • Use timestamps, IDs, tenant, actor, source and intended account to join observations across surfaces.

Last updated: November 2026

Choose the record for the question

An engineer troubleshooting a request must determine what happened at each stage. A request record can show an approval decision. That gets you to the next part of the investigation: what account operation was attempted, on which source, and what did it return? A finished governance process and a managed application showing the intended grant answer different questions. Begin with the actor, recipient, tenant, time zone and approximate execution time. Pinpoint the request, workflow, source, identity or native account ID if it is available. Those details prevent unrelated operations for the same person from becoming evidence for this case.

What you need to seeWhere to start in the documented product
Audit record of a sign-in or administrative configuration changeSearch Events and a relevant audit report or the event details
Reviewer decision and pending approvalRequest or approval administration with the applicable user level
Detailed status or error on one native operationSearch Account Activity and the account/source entry within the activity
Manual provisioning queue and ownerAdmin Dashboard Tasks and the assigned task
Start, finish, counts and errors for a source aggregationThe source's Aggregation History or System Activity details
Workflow path and actual step inputs and outputsWorkflow Executions or Search Workflow History
Configuration deployment outcome by objectConfiguration Hub Activity Log, Deployment Log and Draft detail
Documented identity access changes and datesAccess History timeline and Compare Access, with the relevant source and time constraints

Audit Reports and Monitoring lists the tracked event categories and useful searches. For example, type:AUTH selects recorded authentication events. The Events category is suited to audit evidence for actions the platform tracks. Account Activity contains details for third-party account work, and activity entries can show nested source operations, users, warnings, and attribute results. The overall account action status, its stage, and the status of each nested account request are separate fields. Read the row for the actual source before interpreting the overall result. Identity attribute updates caused by aggregation are not included in the account activity data model. Use aggregation and identity processing evidence for that question.

Work a request failure

Suppose a user can sign in and the correct manager approved the request to grant warehouse access, but the native permission is absent. Open the request to confirm the exact item, recipient and time, then locate the Account Activity entry for the operation. Compare its action, source and account with the affected native account. If there was an error, read the source-specific result. If a manual task was generated, verify the person or group assigned and whether it is still open. Correlate a completed source result with the native account and privilege if fulfillment is disputed. For identities with more than one account, do not infer which account was affected from the recipient's display name alone.

If a workflow started the operation, open its execution and inspect the step result and variables. Creating, editing or enabling a workflow can generate platform audit events. SailPoint's builder documentation distinguishes those events from detailed per-step execution. Search Workflow History can also record the trigger, steps and loop iterations. A workflow status and a downstream account result can be correlated by timing and IDs, with attention to any asynchronous handoff. Similarly, Configuration Hub deployment details can show partial completion. Check each relevant object and reason before replaying a failed deployment.

Check how far back the record goes

Use the correct category and scope when an expected historical record is missing. SailPoint's Search FAQ specifies production Account Activity retention of 60 days or two million actions, whichever is shorter, and staging retention of 30 days or one million actions. Pending access requests and pending account activity are retained indefinitely. The FAQ gives audit events a separate retention period of one year plus the current month. Access History provides an identity's change timeline and date comparisons. Its timeline excludes generic approval events, some tenants lack governance timeline events, and the link from access changes to a governance event has a documented time window. For an older incident, use authorized exports or records retained under the organization's procedure where available. An empty search alone cannot demonstrate that a request never happened.

See SailPoint's audit surfaces, provisioning activity, Search FAQ, search fields, workflow execution records, and Access History.

Test Your Knowledge

A manager approved a warehouse access request, but the privilege is still absent. Which record best identifies the result of the attempted operation on the named native account?

A

The request’s initial creation event.

B

The overall authentication event for the manager.

C

The source and account operation details within the matching Account Activity entry.

D

The configuration audit event recording that the related workflow was enabled.

Test Your Knowledge

A workflow has an error after its second action. Where should an engineer look for the actual input, output, and branch of that action?

A

The execution playback for that run under Workflow Executions.

B

Only the event recording the creation of the workflow.

C

Only the source aggregation count for the day.

D

The public incident status page for the region.

Sections you finish are checked off in the contents.