Web Help Desk Attachment Shows up late on the UI but API shows immediately. Why?

We are running a Web Help Desk instance (`productType=WebHelpDesk`, `productVersion=12.8.3`).

This instance retrieves ticketing data from external systems, requiring us to use the API for updates. While general ticket updates through the API, such as adding notes, work as expected, we encounter an issue with attachments.

When attachments are added via the API, they are reflected in the API responses immediately. However, they do not appear in the UI right away. Users must either wait approximately 5 minutes or log out and log back in to see the attachments. Other updates, such as notes, request details, subject, and custom fields, done via API appear immediately upon page refresh, but attachments do not.

Does WHD have some kind of caching in the background for attachment data? How would I go about fixing/debugging this issue?

Find more posts tagged with

Late

delay

attachments

API

Accepted answers

All comments

pabely

Browser cache is not your friend here

_crimson_

Is the attachment data always retrieved from the browser cache? Data about notes, subject, request detail and other ticket data seem to reflect right away on page refresh.

pabely

I would know how the inner workings of WHD are coded, but I have seen similar for things like Locations, adding new ones do not appear in dropdowns immediately, if you can't wait, logout then in again which must force a re-read from the database.

denzelford

This issue may occur due to UI caching or delayed UI refresh. The API updates immediately, but the front-end may not poll for new data in real time. For example, similar to how a large 85 inch TV may experience slight lag in display updates, the UI needs synchronization. A solution is to implement a forced UI refresh or configure real-time polling to sync with the API updates.