Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
/
Profile import timeout error
Updated Oct 30, 2020

    Profile import timeout error

    Cause

    The profile import timeout error is caused when the process of importing the JEMH profile XML exceeds 20 minuets processing time. This is due to the profile in question being significantly larger than a typical profile or to a network failure. The timeout is set to catch when a network is unresponsive but could also be triggered by a large profile being imported.

    Problem

    This is an issue as JEMH will have imported some amount of the profile in the 20 minuet import window. This will leave your JEMH holding an incomplete profile.

    Solutions

    Before attempting any of these solutions, it is recommended you delete the previous import attempt to remove duplication.

    Reduce the workload

    A solution to assist in the import of your profile is to reduce the demands of the process. This can be achieved by deselecting the options to Auto-create Missing projects, Auto-create Missing Custom Fields, Fix Users, and Fix Issue Types on the profile import screen.

    Depending on the profile, these functions can be very time consuming and may be causing your profile to take to long to process.

    Retry import

    If your profile has partially imported, some of the workload such as project creation has already been carried out. Another attempt at importing may have a reduced workload and be able to import within the time frame.

     

     

    The Plugin People
    Teams
    , (opens new window)

    Knowledge Base
    • How-to articles
      How-to articles
       This trigger is hidden
    Results will update as you type.
    • Enable Auto Labelling
    • Event Listener JSD issue transition notifications do not send if a comment is present in the transition
    • Exception during issue update validation for non-Service Desk issue
    • File Attachments cause Out Of Memory problems
    • Gmail confidential mode
    • How to supply a default value for the Tempo Account custom field
    • How to support email addresses with international characters
    • Issue fails to create with indexing errors
    • JEMH Is not yet licensed through Atlassian Marketplace
    • JIRA fires Issue Assigned event for newly created Issues
    • Jira Service Desk problems
    • Jira 7 *Wrong JVM Version!* Error
    • JSD Organization field
    • Mail fails to be retrieved from mail server
    • MYSQL exception - Caused by: java.sql.SQLException: Incorrect string value
    • MYSQL Duplicate entry '0'. No Valid License
    • Non-JIRA recipient custom field values have been updated but JEMH is notifying the old values
    • Notification History tab does not show on issues
    • Problems with IMAP
    • Problems with POP
    • Slow Jira startup with PostgreSQL
    • Sorry, you can't create any issues right now, as you need to have access to a JIRA application to be able to create issues
    • You do not have permission to assign issues
    • How to change the event type of a notified event
    • Diagnose no inbound mail handled
    • JSD (Jira Service Desk) - Who is notified when?
    • HTML extraction method to Wiki mark up
    • Setting System Fields using Script Field Processor
    • Test case editor fails to load
    • MessageRemovedException in log files during email processing
    • Characters appearing as question marks
    • UI not visible after upgrading to version 3+
    • Default Project Mapping and unwanted inheritance causing inbound mail to be forwarded
    • JEMH is disabled on startup in Manage Apps
    • Configure JSD Customers for use with JEMH
    • Custom Field values are cached causing recipients to not receive notifications (JIRA 7.3.0 - 7.3.4 , JEMH 2.1.0 - 2.1.11)
    • Restrict commenting to one project
    • Foreign key constraint violation during Audit Event history purge
    • Request participants not sent JEMH notification
    • Handling out of disk space
    • Profile import timeout error
    • Zendesk integration
    • Outlook sending formatting
    • Attachment links added as comments, Jira Service Management/Desk
    • Incoming Auditing Actions Error Popup
    • Updating JEMH's issue event listener to listen for IssueEventBundle's (JEMH-6994)
    • Template Set Responsibility Devolution (JEMH-5403)
    • Support non-ascii characters in email addresses (JEMH-6431)
    • Custom Fields don't get added during creation phase causing creation notifications to not fire for User/Group field types. (JEMH-306)
    • Cant stop reporter being added as a watcher (JEMH-790)
    • Handle re-index failure during watcher setup (JEMH-7180)
    • Inline User Macros sometimes don't render (velocity 2.0 needed) (JEMH-5536)
    • "Stuck" emails in queues after post condition test (JEMH-5366)
    • Dealing with 'Undisclosed Recipients' (JEMH Server/DC)
    • Missing Methods in TemplateIssue Class since Jira 8.19.0
    • Why do FolderClosedException occur
    • Customer Permissions for Request Participants
    • User Anonymization Fails - SQL Server 2019
    • Maintaining JEMH Attachment Property Set values
    • Display Issue Notifications in Right To Left Languages
    • Jira Server/DC - when mail polling stops, fixing without a Jira restart
    • A3 BAD User is authenticated but not connected error message when using JIRA with Office365
    • JEMH not enabling on upgrade to Jira 8.13.x and 8.20.x LTS releases made after 23-MAY-2022
    • Using an inactive user with user creation enabled
    • Missing Created/Timestamp Columns Causing Problems
    • -1 Values for the "Comment count limit" and "Comment char length limit" in the Default Project-Mapping
      Calendars
    You‘re viewing this with anonymous access, so some content might be blocked.
    {"serverDuration": 12, "requestCorrelationId": "14220f62f2264e41a48bd9ba8649f2a1"}