Check of Work Requests

The Open Work interface allows you to view all your operations and transactions, including those in progress and pending.

You can monitor and control the operations performed on your domain names following your orders/requests sent to our services and/or your actions on the portal: deposits, transfers, backorders, renewals, contact modifications, etc.

Filters to use for checking the requests that require your attention and/or action on your part.

You can use a filter to easily find the transaction requests that need to be fixed:
"Internal Status", "is", "needs attention" and "missing information".

 

Explanation of the status of the work requests:

  • New (:new): The request has been added to the customer's cart, but has not yet been submitted.
  • Incomplete (:incomplete): Waiting for further input. This may be the case for "complex" domain orders that require information, or requests that have just been saved for further completion.
  • In review (:review): Waiting for authorisation; see above. From here, a task can be authorised (making it in progress), sent back to incomplete state with annotations, or aborted.
  • Queued (:queued): The request has been put on a queue and is waiting to be picked up by an operator at SafeBrands side. This state should normally only last for a few seconds/minutes, in some rare cases worstly longer.
  • In progress (:processing): The system is processing the task in the background. If errors happen, the request may go back to the incomplete state if the issue can be fixed by the user, or it could just be aborted. A request going back to a user must be idempotent, i.e., it must not leave behind stray side effects like invoice items or stale domain objects. If a work request is not handled in realtime, it will remain in this state and wait to be closed by an incoming event or by fulfillment.
  • Limbo (:limbo): (needs attention) An error occurred while processing the request. This usually means that a notification has been sent by mail, and in most cases, useful information should be attached.
  • Failed (:failed): The request could not be fulfilled for some reasons. All parties have been notified about the details.
  • Finished (:finished): The request has been successfully processed by the system. All parties have been notified.