The application workflow
From a listing to a submitted application.
This is the full path an application takes, from a scraped listing to a tracked outcome. Each stage names where the work happens: on Applivo's servers, on the website, or in your browser through the extension.
- A job is scraped and analyzed (server).
- You queue it on the Jobs page, or auto-queue creates the application (server).
- If manual approval is on, it waits as Pending approval until you approve it (website).
- With an eligible plan and a connected extension, you start a run and select the queued applications (website).
- The server creates the run and records whether automatic submission is authorized (server).
- The extension opens each application form in your browser, fills it, and validates it (browser).
- The portal confirmation is checked; the application is marked Applied only when the portal confirms (browser to server).
- Outcomes recorded later by the portal flow back into the application's status (server).
End-to-end application lifecycle
public/docs/images/docs-application-lifecycle.png
What happens when a step fails
| Failure point | Effect | Recovery |
|---|---|---|
| No eligible plan / no extension | Run cannot start | Subscribe to an eligible plan and connect the extension |
| Required question has no safe answer | Item stops as waiting for input | Answer it manually, then retry |
| Portal session expired | Item cannot reach the form | Sign in to Internshala again and retry |
| CAPTCHA appears | Item stops for you | Solve it in the browser when prompted |
| Portal gives no confirmation | Outcome recorded as unknown | Check Internshala before retrying |
The extension steps are detailed in Starting an application run and Submission results and duplicates.