# ariba questionnaire submission timed out: how to fix it

An Ariba questionnaire submission that times out is usually a big questionnaire, a slow connection, or a session that aged out during answering. Save as draft, refresh the session with a fresh login, then submit. Splitting very long questionnaires into saved chunks beats one giant submit.

```text
ariba questionnaire submission timed out
```

## When to use this skill
- Questionnaire submit spins and then times out
- Long questionnaires die near the end

## When not to use this skill
- Submit is instant but errors (a validation issue)
- The questionnaire page itself wont load (a portal issue)

## Tool compatibility
SAP Ariba sourcing questionnaires.
Related area: business SaaS platforms and vendor portals.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with questionnaire submit spins and then times out, start at step 1 below.
- If instead submit is instant but errors (a validation issue), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Save the questionnaire as a draft

```
Use the save draft option before the session fully dies.
```
Expected: draft saved with your answers intact.

### 2. Refresh your session

```
Log out and back in to get a fresh session.
```
Expected: clean login, no stale state.

### 3. Reopen and review

```
Open the draft and skim for any answers lost in the timeout.
```
Expected: all answers present.

### 4. Submit in one go

```
Submit promptly without long idle gaps.
```
Expected: submission confirmation.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (save the questionnaire as a draft): Expected: draft saved with your answers intact.
- Step 2 (refresh your session): Expected: clean login, no stale state.
- Step 3 (reopen and review): Expected: all answers present.
- Step 4 (submit in one go): Expected: submission confirmation.

## Quick recap
1. Save the questionnaire as a draft
2. Refresh your session
3. Reopen and review
4. Submit in one go

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### ariba questionnaire wont submit timeout
Save draft, fresh login, prompt submit. If this matches what you saw, the steps above apply as written.

### questionnaire submission timed out ariba
Long questionnaires are the trigger, chunk your work. If this matches what you saw, the steps above apply as written.

## Why it happens
Questionnaire submits are single large requests. On slow connections or with hundreds of answers, the request outruns the server or session timeout, and the whole submit is lost instead of partially saved.

## Edge cases
- Answers with huge pasted text blocks inflate the request, trim them
- File uploads inside questionnaires add the most time, attach them early
- Draft saves are your checkpoint, use them every 10 minutes

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_JMc3_FYjniIqK1oZbZyYmA
