Submitting online vs. offline
When you submit a form while you’re online, Air Fill writes the record straight to your Airtable base.
When you submit while you’re offline, or the connection drops partway through, Air Fill saves the submission and shows:
“Saved offline — we’ll submit it automatically when you’re back online.”
There’s nothing else to do. Once you’re back on a connection, Air Fill sends it for you.
Forms with attachments
Attachments can’t be queued offline. If a form includes attachments and you’re offline, you’ll see:
“Attachments need a connection. Reconnect to submit this form.”
Reconnect, then submit the form again.
Where queued submissions live
Queued submissions wait in the History tab, marked with a clock icon. When items are waiting, the tab shows a badge with the number still to send. There’s no separate queue or outbox screen — the queue is simply the waiting items in History.
Each item in History shows its status with a coloured dot:
- Synced (green) — the record reached your base.
- Queued (warning) — the submission is saved and waiting to send.
- Failed (red) — Air Fill couldn’t confirm this one (see below).
Items that need a look from you are grouped at the top under Needs attention.
When sync happens
Sync is automatic. Air Fill sends queued submissions:
- when you reconnect to the internet,
- when you open the History tab,
- when you pull to refresh,
- and when you reopen the app.
It also tries from time to time in the background. iOS decides the exact timing there, so treat background sync as a helpful extra rather than a set schedule. If you want something sent right away, open History or pull to refresh.
Drafts vs. queued submissions
These two are easy to mix up, and they’re different things.
- A draft is a form you’ve started but haven’t submitted yet. Air Fill can save it so you can come back and finish — a form tile shows Draft saved.
- A queued submission is a form you’ve already completed and submitted. It’s waiting in History to reach Airtable.
Put simply: a draft still needs you to finish and submit it; a queued submission is done and on its way.
If an item shows “Failed”
Sometimes a connection drops at just the wrong moment and Air Fill can’t tell whether your submission reached Airtable. When that happens, it marks the item Failed and shows:
“We couldn’t confirm this went through. Check your table before submitting again — it may already be saved.”
A Failed item may or may not have saved to your base. Open your Airtable table and check before you resend, so you don’t create a duplicate.
Managing items in History
Swipe an item in History for quick actions:
- Retry — offered for failed items, to send again.
- Delete — remove the item from your history.
Queued items don’t need a Retry; they sync on their own.
Open an item to see its details, where you’ll also find:
- Resend to Airtable — creates a new record in your base.
- Delete from history — removes the item.
Because Resend to Airtable creates a new record, check your table first if the original may already have saved.
Good to know
In this version, Air Fill only creates new records while you’re offline. Editing an existing record needs a connection.