# agent loop detected re-submitting same ariba form after failed submit: how to fix it

An agent re-submitting the same Ariba form after a failed submit is looping because it never reads the failure reason. Capture the submit error, fix the named problem, and submit once. Blind resubmission of a deterministic failure just repeats it.

```text
agent loop detected re-submitting same ariba form after failed submit
```

## When to use this skill
- An agent resubmits an Ariba form repeatedly
- Logs show identical submit attempts

## When not to use this skill
- Submits fail differently each time (a flaky portal)
- The form validates but the portal errors (a portal issue)

## Tool compatibility
Agent Ariba form automation with submit handling.
Related area: agent frameworks and agent runtime tooling.
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 an agent resubmits an Ariba form repeatedly, start at step 1 below.
- If instead submits fail differently each time (a flaky portal), 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. Capture the submit failure

```
Read the full error from the failed submission attempt.
```
Expected: a specific reason, like a validation error.

### 2. Fix the named problem

```
Correct whatever the error describes in the form.
```
Expected: the form validates cleanly.

### 3. Submit exactly once

```
Submit a single time and read the result.
```
Expected: success or a new specific error.

### 4. Cap submit attempts

```
Allow at most three submits per run before escalating.
```
Expected: the agent stops instead of looping.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (capture the submit failure): Expected: a specific reason, like a validation error.
- Step 2 (fix the named problem): Expected: the form validates cleanly.
- Step 3 (submit exactly once): Expected: success or a new specific error.
- Step 4 (cap submit attempts): Expected: the agent stops instead of looping.

## Quick recap
1. Capture the submit failure
2. Fix the named problem
3. Submit exactly once
4. Cap submit attempts

## 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
### agent resubmitting ariba form loop
Read the error, fix it, submit once. If this matches what you saw, the steps above apply as written.

### ariba form submit loop
Deterministic failures need fixes, not retries. If this matches what you saw, the steps above apply as written.

## Why it happens
Form validation failures are deterministic: the same data fails the same rule every time. An agent that resubmits without reading the error repeats the failure, mistaking activity for progress.

## Edge cases
- Screenshot the error, messages can vanish on navigation
- Some failures need buyer-side fixes, escalate those
- Log every submit attempt with its result

## Provenance

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