Singapore Postings: Occupation coding

Resolved
Resolved

We've now resolved the incident. Thanks for your patience.

Updated

Unfortunately, there was an issue with the pipeline release on Wednesday, August 16th, 2023. This pushed back the fix for the Occupation coding in Singapore, Australia, and New Zealand affecting Global Postings. The new estimated release is targeted for deployment by Friday, August 18. We apologize for any inconvenience this has caused.

Updated

There was an issue with the pipeline release on Friday, August 11th, 2023. This pushed back the fix for the Singapore Occupation coding affecting Global Postings. The estimated release is targeted for deployment by end of day Wednesday, August 16th, 2023.

Updated

We have identified that this issue is also affecting Australia and New Zealand. We expect this will be fixed on the same timeline as Singapore postings (Friday August 11th, 2023) but cannot confirm at this moment.

Updated

The fix to correct the missing coding for the Occupation fields has been delayed to the next pipeline release scheduled for Friday August 11th, 2023.

Recovering

We've fixed the core issue, and will correct the missing coding for the Occupation field with the next pipeline release scheduled for Friday July 28th, 2023.

Identified

We are currently experiencing a issue in populating coding for occupations in Singapore data. We are working to resolve this problem.

OCCUPATION and OCCUPATION_NAME fields are not being classified.

Began at:

Affected components
  • API
    • Job Postings API
      • Global Job Postings API
  • Snowflake
    • Postings Global