You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had to put a production quick fix for vdthess24 today, because HoL90 (id=5351) was not present in event-descriptor's talkFormats entry (I added the entry manually to resolve the issue)
It seems that the event-descriptor was not being overwritten. It appears that a new event descriptor may have been created during the initial crawl and not updated subsequently. This requires further investigation to ensure that the event descriptor is updated upon new crawls.
While this is a rare occurrence, there is a possibility that a new talk format may be added after the voxxrin schedule has been created.
The text was updated successfully, but these errors were encountered:
Need to investigate further once vthess24 is over, because when I try to delete HoL90 entry locally, and re-trigger a new crawling, HoL90 is re-added to the event-descriptor entry (it was not the case in prod)
There is certainly another problem upstream to the event-descriptor save
This seems to be related to an already-fixed issue (in c0d1783) but not deployed in prod yet (as I was in a Devoxx BE + Voxxed Thess24 freezing period)
Will wait for the deployment (post voxxed thess24) to check if this is fixed to close the issue
I had to put a production quick fix for vdthess24 today, because HoL90 (id=5351) was not present in event-descriptor's
talkFormats
entry (I added the entry manually to resolve the issue)It seems that the event-descriptor was not being overwritten. It appears that a new event descriptor may have been created during the initial crawl and not updated subsequently. This requires further investigation to ensure that the event descriptor is updated upon new crawls.
While this is a rare occurrence, there is a possibility that a new talk format may be added after the voxxrin schedule has been created.
The text was updated successfully, but these errors were encountered: