The portal ends a session after a period without activity, and unsaved work is lost. During busy seasons this can cost hours. This episode explains how to work so that a session ending never costs more than one record.
The short version
- Prepare data offline first, in one spreadsheet.
- Enter in small batches and save after each farmer.
- Work at quieter times, such as early morning.
- If a session ends, log in again and check the last saved record.
Why Sessions End
For security, the portal ends a session after a period without activity; unsaved entries are lost.
Government portals end inactive sessions to protect accounts. Typing slowly from paper, or leaving a form open while checking records, can count as inactivity. When the session ends, anything not saved is lost.
Working Safely
Prepare offline, work in small batches, and save after every farmer.
- Prepare offline.Put every farmer's data in one spreadsheet, checked, before opening the portal.
- Small batches.Enter a few farmers at a time.
- Save after each farmer.Do not wait to finish the group.
- Keep a tick list.Mark each farmer in the spreadsheet as it is saved.
Illustrative workload. At about three minutes per record, 50 farmers take 150 minutes. Saving after each one means a session ending costs at most one record.
When a Session Ends
Log in again, find the last saved record, and continue from the tick list.
- Log in again.
- Open the last farmer on your tick list and check what was saved.
- Re-enter only what is missing.
- Continue, and consider working at quieter times, such as early morning.
Portal screens and messages change from time to time. If an option described here is missing, ask your Regional Council, or the PGS-India Secretariat at the National Centre for Organic and Natural Farming.
Check yourself
Tap an answer to see whether you are right, and why.
What limits the damage when a session ends?
- Entering the whole group before saving
- Saving after each farmer
- Using two browsers
Then a session ending costs at most one record.
Where should data be prepared before entry?
- Directly on the portal
- In one checked spreadsheet
- On paper only
Typing from paper is slow and error-prone.
Remember these things
- Prepare offline.
- Small batches.
- Save after each farmer.
- Keep a tick list.
Saving as you go turns a lost session into a minor delay. KrushiFlow validates these fields and submits farmer records to the portal in bulk.