Aller au contenu principal

Retry an order so Hyperfox reads it again from the start

  • Utilisateur
  • Admin

Retry an order when Hyperfox must read it again from the start. Retry acts on the whole inquiry, the document the order came from. Retry deletes every order of the inquiry, including the changes you saved, and replaces them with a new reading. If you are new to the path of an order, read How an order reaches your ERP first.

Use Retry when the e-mail was sent to the wrong route or the order arrived without data. Also use Retry when your admin changed an instruction and wants to test it. Retry is never the way to fix one field that was read wrong. To fix one field, correct that field and validate.

Check before you start​

What Retry does:

  • Retry sends the inquiry back for a new reading, which creates the orders again.
  • The new run reads the document again, with the AI mapping and Codex as they are now. It can read the document differently from the first run: other values, other lines or another number of orders. Its result can be better or worse.
  • Retry records nothing in Codex. Only Validate records your corrections. A correction you made before a retry is gone, and Codex has no entry for it. How Codex learns from your corrections explains how it records corrections.
  • Retry keeps the inquiry. If you forward the e-mail to Hyperfox again instead, Hyperfox creates a second inquiry, which you then reject. That case is covered in Two inquiries with the same order in To validate.

When Hyperfox offers Retry:

  • Retry is on the validation screen, not in the lists.
  • Every order of the inquiry is Pending Validation or Saved. When an order is validated, rejected or sent to your ERP, Hyperfox does not run the retry. This also applies when the order returned with Submit Failed. A new run has no record of what your ERP already received.
  • Nobody else has the inquiry open. When a colleague has it open, your screen is read-only and has no Retry. What happens when you and a colleague open the same order explains the lock.

What Retry shows:

  • On an inquiry that arrived by e-mail, through a channel with two or more routes, Retry opens a menu. Retry with current category reads the e-mail again with the same route as the first time. Below it, each route of the channel has an entry with its name, and a check mark shows the current route.
  • On any other inquiry, Retry starts without a menu. Examples are an inquiry that arrived by API or EDI, or through a channel with one route.
Retry discards your edits

Retry deletes every order of the inquiry, including the changes you saved, and replaces them with a new reading. Retry also deletes the orders you added. This cannot be undone. To keep your changes, correct the order by hand and validate it instead.

Retry an inquiry​

  1. Open the inquiry from To validate.
  2. Click Retry. If no menu opens, the retry starts. Hyperfox shows "Retrying" and returns you to To validate.
  3. In the menu, click Retry with current category or the name of the right route. Retry with current category keeps the route. The name of another route reads the e-mail with that route. Hyperfox shows "Retrying" and returns you to To validate.

What you see afterwards​

  • The inquiry is in Processing until the new run is done, and then returns to To validate with the orders of the new run.
  • A colleague who still had the inquiry open cannot save their changes on the old orders. They get the message "This inquiry was reprocessed since you opened it.".
  • Before you validate, check every order of the new run against the document, also the values that were right before. If the new run gave two orders where the first run gave one, the fix is in One mail gave two orders that should be one.
  • If the order arrives empty again, fill it in by hand from the document and validate it. Then report the inquiry id to support. The order arrived without data covers this case.
  • The new run replaces the orders and never adds to them. If the inquiry shows the orders of both runs side by side, do not validate either set. Report the problem to support with the inquiry id. How to report a problem with an order to support lists what to send.

When Retry is refused:

What you seeWhyWhat to do
"Retry failed"An order of the inquiry is no longer Pending Validation or Saved, or the route no longer belongs to the channel.Refresh the inquiry and check the order statuses.
"This inquiry is being processed again."You or a colleague already retried it.Wait until it is back in To validate.
A colleague's name, "has this inquiry open since" and a timeA colleague has the inquiry open. Your screen is read-only and has no Retry.Ask them to close it. Details in The screen is read-only: a colleague has the inquiry open.

See also​

Dernière mise à jour le