Motaded متعدد
عربي Get early access

When a submission result is unclear

A missing confirmation does not prove that nothing happened. Check the original attempt before taking an action that could create another request.

4 min read

An official action can reach a service even when the response does not reach Motaded. A timeout, interrupted connection or unavailable status can therefore leave the outcome uncertain. Treat this as a verification task rather than an instruction to submit again.

Who does what

  • Motaded

    Shows the available result and any supported status-check or recovery action.

  • Relevant authority

    Holds the official request or transaction if it was received.

  • Authorised account holder

    Checks the correct account and company context.

  • Support team

    Helps investigate unresolved discrepancies using the available request and attempt information.

In what order

  1. Pause further submissions

    Do not create another application or repeat the same official action while the original outcome remains unclear.

  2. Identify the original attempt

    Note the company, procedure, approximate time and any reference or message shown. Keep the context available for checking.

  3. Use the available status-check process

    Follow the request’s indicated next action. If account verification is required, restore the correct access before checking again.

  4. Check the relevant official account where needed

    Look for a matching request or transaction. Compare the company, procedure, applicant and timing rather than relying on a similar title alone.

  5. Continue according to the confirmed state

    If a request exists, follow its current state. If no outcome can be established, keep investigating rather than treating an empty list as proof of failure.

  6. Ask for help when the result remains unresolved

    Provide the request context and the message received. Do not include passwords, verification codes or unnecessary personal documents.

Unconfirmed vs confirmed failure

Receipt unconfirmed

  • The available response does not establish whether the action succeeded
  • An official request may already exist
  • Further checking is required
  • Repeating the action may create a duplicate

Failure confirmed

  • Available evidence establishes that the action did not complete
  • The cause may need correction
  • The relevant workflow determines whether retrying is appropriate
  • Any retry still needs the correct account and company context

Gather the information needed to check

  • Company or applicant

    Identify the entity or person the attempt concerned.

    Application

  • Procedure

    Record the action that was attempted.

    Relevant workflow

  • Attempt time

    Keep the approximate time and timezone where known.

    Attempt details

  • Reference

    Retain any local or official reference, distinguishing between them.

    Motaded / authority

  • Message received

    Preserve the relevant error or uncertainty message.

    Application response

  • Verification result

    Record what the subsequent check established.

    Status check / official account

Mistakes to avoid

  • Treating a timeout as a rejection.
  • Repeating the action from another browser tab or account.
  • Creating a new draft to bypass an uncertain request.
  • Assuming no visible record means no request was received.
  • Treating a payment confirmation as proof of every related application outcome.

FAQ

No. It means the expected response was not received in time. The application may or may not have reached the authority.

Resolve the existing attempt before starting another

Contact the team with the affected company, procedure and available reference if the outcome remains unclear.

Contact our team