Hi Adrianto,

Thanks for reaching out and for describing the issue clearly.

It sounds like your integration messages are getting stuck at the "Received" status and not progressing to "Processed." This typically means Maximo encountered an error during processing. Here's a step-by-step approach to help you resolve this:

1. Check Message Details and Error Data

·        Go to the Message Reprocessing application.

·        Select the affected message and click the pencil (edit) icon to view the message details.

·        Review the Error Data section for any validation errors, missing fields, or data mismatches. This often points directly to what's preventing processing.

2. Review System and Application Logs

·        Check the Maximo application logs (such as SystemOut.log and SystemErr.log if you're using WebSphere).

·        Look for error messages around the time the integration ran. These logs often provide specific reasons for failures (e.g., data validation issues, missing references, or configuration errors).

3. Verify Data Consistency

·        Double-check that the data coming from your external system matches what Maximo expects.

·        For example, if you're integrating with ArcGIS and trying to update an asset, make sure the asset exists in Maximo and is in the correct status (e.g., ACTIVE, not CLOSED).

·        If there's a mismatch (like the asset is CLOSED in Maximo but ACTIVE in ArcGIS), update the status in Maximo as needed.

4. Check Integration and Cron Task Configuration

·        Ensure that relevant Cron Tasks (such as JMSQSEQCONSUMER or file consumers) are running and not paused.

·        Confirm that Admin Mode is OFF, as integrations won't process while it's enabled.

·        Verify that your message tracking and integration properties are correctly set in Maximo.

5. Reprocess the Message

·        After correcting any data or configuration issues, return to the Message Reprocessing app.

·        Edit and save the message if needed, then click Process to reattempt processing.

·        Alternatively, you can wait for the next integration cycle if your system is set up for automatic retries.

6. Communicate with Stakeholders

·        Let your team and relevant business users know about the root cause and the corrective actions taken.

·        If this is a recurring issue, consider reviewing your integration and data governance processes to prevent future problems.

Reference

For more details, see IBM's documentation on Reprocessing an Edited Message.

Summary:
Messages stuck in "Received" status are usually due to data or configuration issues. By checking the message details, reviewing logs, correcting any mismatches, and reprocessing, you should be able to resolve the issue. Always keep stakeholders informed about the resolution and any actions required on their end.

If you need more specific help after checking the logs or error data, feel free to share the error message here, and I can help you further troubleshoot.

Best regards,
Agustina