Overview
A session is a single execution run of a . Every time one of your automations runs — whether on a schedule, triggered by an event, or started manually — Friday creates a session to track the execution from start to finish. You can view all sessions by clicking Sessions in the left sidebar.Viewing session history
Friday provides two ways to view session history:- All sessions: Click Sessions in the left sidebar to see a chronological list of every automation run across all your Spaces.
- Per-Space sessions: Open a Space to see only the sessions belonging to that specific automation.
- The Space that ran
- When the session started and completed
- The current status (running, completed, or failed)
Session detail
Click on any session to see the full execution detail. A session shows:- Execution steps — Each action Friday took during the run, including which tools and integrations were used. Steps are the individual operations (like fetching data, sending a message, or processing a file) that make up a session.
- Timeline — A chronological view of when each step started and finished.
- Results — The output generated by the automation (reports, messages sent, data processed).
- Errors — If something went wrong, the specific step that failed and why.
Monitoring active sessions
When an automation is currently running, you can watch its progress in real time. Open the active session to see each step as it executes. The session view updates live, so you can follow along as Friday processes data, calls integrations, and generates output.Debugging failed sessions
If a session fails, the session detail view shows exactly where and why:Open the failed session
Find the failed session in the Sessions list. Failed sessions are marked with an error status.
Identify the failing step
Look for the step marked with an error indicator. This shows exactly which operation failed during the run.
Common failure causes
Expired integration tokens
Expired integration tokens
The OAuth token for a connected service has expired or been revoked. Go to Settings → Integrations, remove the affected integration, and reconnect it by asking Friday to perform an action with that service.
Third-party API rate limits
Third-party API rate limits
The connected service is rejecting requests because too many were made in a short period. Friday will typically retry automatically after a short delay. If the issue persists, consider reducing the frequency of your automation.
Changed data formats or permissions
Changed data formats or permissions
The structure of data returned by a connected service has changed, or your permissions on that service have been modified. Review the error details and update your automation or re-authorize the integration as needed.
If an automation fails repeatedly, you can ask Friday in chat to help diagnose and fix the issue. Describe the problem and Friday will suggest changes.