> ## Documentation Index > Fetch the complete documentation index at: https://docs.athenahq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Pitch Success (Processing) Page > Show a waiting/processing screen right after a pitch report is created, auto-redirecting into the finished report once it's ready. `app.athenahq.ai/pitch-workspace/success` ## Purpose The Pitch Success page serves as a waiting room immediately after a customer submits a new pitch report. Because pitch reports require comprehensive AI processing that typically takes 5 to 10 minutes, this page sets expectations, shows a simulated progress indicator, and automatically redirects the user to their completed report once the backend finishes its work. It allows customers to either wait for the final result or immediately jump to other tasks. ## What's on the page **Loading skeleton state** A temporary placeholder (a title bar shape and two lines of text) shown briefly while the app looks up the newly created pitch in the browser's memory. **Pitch Created card** The main container confirming that the pitch was successfully submitted. It includes a brief explanation that processing usually takes 5-10 minutes. **Progress indicator & Progress bar** An animated, pulsing indigo dot paired with the text "Processing your data...". Below this is a horizontal progress bar (indigo fill). This is a time-based visual estimate of how far along the processing is, rather than a live percentage from the server. **Action buttons** Two large buttons offering users an exit ramp if they don't want to wait on this screen for 10 minutes. **Footnote** A small text note at the bottom stating, "We'll automatically redirect you when your report is ready," reassuring users that they don't need to refresh the page manually. ## What you can do here * **Wait for completion**: Users can simply leave the tab open. The page checks the server in the background every 5 seconds. Once the report is ready, it automatically navigates to the Pitch Workspace. * **Create Another Pitch**: Clicking this primary button navigates directly back to the pitch creation form so the user can queue up another report immediately. * **View Report (May Still Be Processing)**: Clicking this secondary button forces the app to jump to the Pitch Workspace right away, allowing the user to look at the partial data generated so far. ## Data shown * **The active pitch**: The page relies on the browser's session memory to know which pitch was just created. * **Processing status**: The page regularly asks the server for the current status of the pitch to determine when to trigger the automatic redirect. ## Common workflows **Wait for automatic redirect** 1. The user lands on this page right after submitting a new pitch. 2. The progress bar steadily fills based on the time elapsed since the pitch was created (capping at 95%). 3. The page silently checks the pitch status every 5 seconds. 4. When the server reports the status as "completed," the progress bar jumps to 100% and the browser automatically redirects to the Pitch Workspace after a brief half-second delay. **Skip waiting and create another pitch** 1. The user decides not to wait on the processing screen. 2. They click **Create Another Pitch**. 3. The app immediately navigates to the pitch creation form to start a fresh workflow. **Skip waiting and view the in-progress report** 1. The user clicks **View Report (May Still Be Processing)**. 2. The app clears out its cached pitch data to ensure it has the freshest available information. 3. The browser navigates to the Pitch Workspace, where the user can view whatever partial data has been processed so far. **No active pitch found** 1. The page loads but cannot find a record of a recently created pitch in the browser's memory. 2. Without waiting, the page automatically redirects the user back to the pitch creation form so they don't get stuck on an empty processing screen. ## Empty, loading, and error states * **Loading**: While the app is verifying which pitch to monitor, users see a skeleton loading card. * **Empty**: If the page determines there is absolutely no pitch to track, it bypasses showing an empty state entirely and redirects the user to the creation page. * **Error**: There is no explicit error banner or failed state shown on this screen. If the background status check returns an error, the page simply stops checking the status. The user will need to use one of the action buttons to navigate away. ## Linked from / links to * **Linked from**: Users are brought here automatically from the **Create Pitch** flow immediately after submitting a new pitch. * **Links to**: **Create Pitch** (to start a new one) and the **Pitch Workspace** (to view the report). ## Common support questions **Why is my progress bar stuck at 95%?** The progress bar is a time-based estimate that assumes the pitch will take exactly 5 minutes. It caps at 95% to avoid showing 100% before the report is actually done. If the servers are under heavy load and processing takes longer than 5 minutes, it will sit at 95% until the final completion signal is received. **Is it safe to close this tab?** Yes. The pitch is being processed securely on Athena's servers. Closing the tab, navigating away, or clicking the action buttons will not interrupt or cancel the pitch report. **I clicked "View Report" but my data is missing. Did it break?** No. If you bypass the waiting screen using the "View Report (May Still Be Processing)" button, you are intentionally viewing the report before it has finished generating. Some charts or data points will be empty until the backend finishes processing.