Attachments Uploaded via API Not Displaying Until Manual Update

API & SDK
1

Originally posted by khushboo

Dear ServiceM8 Support Team,

I am experiencing an issue with attachments uploaded to job records via the API. Previously, these attachments would appear in the attachment section within approximately 15 seconds. However, for the past month, the attachments do not display until a new note or file is manually added to the attachment section.

I have reviewed the API implementation and ensured that it aligns with the guidelines provided in the ServiceM8 Developer Documentation. Despite this, the issue persists.

Could you please assist in identifying the cause of this delay and provide guidance on how to resolve it?

2

Hi khushboo,

I understand you’re experiencing delays with attachments appearing in the interface after API uploads. We’ve tested the attachment upload process using the example provided in our documentation, and the files appear as expected.

To help narrow down the issue, could you please confirm:

  1. Do the attachments appear after simply opening and closing the job?
    2. Or do you need to make a change to the diary even after closing/reopening to see the files?

This information will help us better understand the specific behavior you’re experiencing and provide more targeted assistance.

Thanks,
Cody

3

Hi Cody, we are not able to see the attachment even after closing / reopening the job window. It only starts showing up once we add a manual note / manually upload some attachment .. basically take some action to trigger the Diary refresh manually via the service m8 interface.

4

Can anyone pls advice?

5

Can anyone pls advice?

6

Hi Jitesh,

Thank you for this additional information. I understand that even closing and reopening the job window isn’t resolving the issue. Let’s try a more specific approach to force the refresh:

  1. After uploading the attachment, make a PUT request to the job endpoint with a status update. For example, you can update the job’s status to its current value:```
    PUT /api/v2/job/{uuid}
    {
    “status”: “current_status”
    }

  2. If you’re using the attachment upload endpoint, ensure you’re receiving a successful response code (200 OK) and waiting for the upload to complete before proceeding.

If this workaround doesn’t resolve the issue, we’ll need to escalate this to our development team for further investigation. Please let me know the results after trying these steps.

Thanks,
Cody