Admin Portal for Mobile - Submission Tracking and Error Handling

Track mobile app user Submissions in the Admin Portal in real time, filter by status, and diagnose failures using the error message returned by the FAMIS 360 API. You can:

  • Review all mobile submissions from the last seven days, including submission type, feature, record ID, and status.​

  • Filter submissions by status: All, Pending, or Failed.​

  • See each submission’s progression, including Completed, Ready, or Waiting for authorization.​

  • View submission data and message to pinpoint the cause for failed submissions.​

Session behavior and security

  • View session details (last authentication time, device type, app version, and session activity) on the Users page to diagnose login issues.​

  • Session activity refreshes about every 10 minutes due to the FAMIS auth token policy. Use the refresh and expiration logs to investigate frequent logouts.​

  • If you see repeated session expirations, review the user’s device/app version and recent activity to isolate the cause.​

View recent submissions

  1. In the Admin Portal, select the user.

    Within the user view, the recent submissions display in the bottom middle portion of the user view.​

  2. Review the list of recent submissions. Each entry shows the submission type, feature, record ID, and current status for the last seven days.​

Filter by status

  1. In Submissions, select a filter: All, Pending, or Failed.​

  2. Review the filtered results to focus on items that are in progress or require attention.​

Review a submission’s progression

  1. Select a submission to open its details.

  2. Check the progression state, such as Completed, Ready, or Waiting for authorization, to understand where it is in the process.​

Investigate failed submissions

  1. Filter by Failed.

  2. Select the submission to open its details.​

  3. Review the submission data and messaging to identify the cause (for example, a permissions issue or invalid data).​

  4. If the failure appears related to user context, use the Users area to:

    1. Review the user’s last authentication time, device type, app version, and recent session activity.​

    2. View and clear user-set filters that might hide or restrict data needed for the submission.​

    3. Review cached collections and lists, or delete/download cached data for analysis.​

    4. After addressing the cause, have the user update the record from the mobile app and submit with the record changes.

Retention and scope

The Submissions list retains the last seven days of mobile activity. If you need to investigate older items, capture details promptly or reproduce the issue.