My table isn’t accepting responses
You open a Dailybot table link or flow to add a row, but submit is disabled, the form errors, or the bot says the table is closed. Tables enforce lifecycle rules: active windows, response caps, and permissions. Most “won’t accept” reports are policy, not corruption.
Quick check
- Expiration — Confirm the table is still within its open dates or submission deadline.
- Response limit — See whether the owner set a maximum number of responses or rows.
- Permissions — Verify you are logged into the account that is allowed to answer (org member vs guest).
- Required fields — Incomplete required cells block save; scroll for field-level errors.
- One response rule — Some tables lock after your first successful submission.
Common causes and fixes
Table expired
After the closing time, new submissions are rejected to preserve snapshot integrity. Owners can extend or duplicate the table if your workflow allows; see Table expired before everyone responded. Participants should refresh the page after the owner publishes new dates.
Response limit reached
Campaign-style tables stop at N responses to cap incentives or review workload. Ask the owner to raise the cap, archive old rows, or spin up a new table for the next cohort. If you hit a per-user limit, the owner must adjust that setting.
Permissions
Guests, contractors, or users outside the connected workspace may be blocked. Admins should confirm the table’s audience matches the people invited. Role changes mid-cycle can remove access; re-share the link after roles update.
Validation errors
Strict formats (email, number, select-from-list) reject silent failures on mobile if error text is off-screen. Zoom out, use desktop, or ask the owner to relax validation for free-text emergencies.
Concurrent edits
Two people editing the same row can produce a conflict error that looks like a generic failure. Retry after refreshing; owners can enable clearer locking if available in your plan.
If none of this worked
Before contacting support, gather:
- Table name or share link (redact tokens if sensitive)
- Exact error text or screenshot
- Your role in the organization
- Browser and device
- Whether others can still submit
- Steps you already tried from this article
Then contact Dailybot support from the Help or Contact options in the product or on the website.