Summary
Four tests under tests/test_profile.py expect the Sync file-parsing endpoint to return 201 Created, but get 202 Accepted with the server message:
Your profile has been successfully sent to the Parsing Queue. Please enable real-time Sync parsing for this Source, please send us your source_key in the chat or contact sales.
Affected tests:
Root cause
The sources pointed to by HRFLOW_SOURCE_KEY_QUICKSILVER_SYNC and HRFLOW_SOURCE_KEY_HAWK_SYNC aren't actually configured for real-time Sync parsing on the test account — the backend falls back to async queue handling (202) instead.
Suggested fix
Either (a) document that these env vars must point to Sync-enabled sources and add a clearer skip/error when they don't, or (b) relax the assertion to accept the 202 fallback, or (c) set up Sync parsing on the dedicated test account.
Summary
Four tests under
tests/test_profile.pyexpect the Sync file-parsing endpoint to return201 Created, but get202 Acceptedwith the server message:Affected tests:
test_profile_parsing_file_quicksilver_sync_basic(tests/test_profile.py:152)test_profile_parsing_file_hawk_sync_basic(tests/test_profile.py:242)test_profile_parsing_hawk_sync_png(tests/test_profile.py:666)test_profile_parsing_hawk_sync_docx(tests/test_profile.py:684)Root cause
The sources pointed to by
HRFLOW_SOURCE_KEY_QUICKSILVER_SYNCandHRFLOW_SOURCE_KEY_HAWK_SYNCaren't actually configured for real-time Sync parsing on the test account — the backend falls back to async queue handling (202) instead.Suggested fix
Either (a) document that these env vars must point to Sync-enabled sources and add a clearer skip/error when they don't, or (b) relax the assertion to accept the 202 fallback, or (c) set up Sync parsing on the dedicated test account.