When a report is submitted for processing or for web print with EFO/Test EFO, if the dotFEC file is larger than 20MB, EFO returns that the file is “processing” and our API begins polling. When polling, our back-end periodically asks EFO if it’s done processing. Two environment variables, EFO_POLLING_INTERVAL and EFO_POLLING_MAX_DURATION, control how long our back-end waits between requests and how long polling will last before considering the task “failed” (values measured in seconds).
These environment variables currently have placeholder values (30 seconds and 300 seconds, respectively), and we need to work with the FEC to determine the best values for DEV, STAGE, and TEST going forward. Once we have those numbers pinned down, we can simply update our manifest files to implement them.
akhorsand commented: [~accountid:712020:2a1493e5-adee-45bd-b27e-868a5c8d3f62] this is the ticket to implement the finalized limits for polling, per the email chain.
When a report is submitted for processing or for web print with EFO/Test EFO, if the dotFEC file is larger than 20MB, EFO returns that the file is “processing” and our API begins polling. When polling, our back-end periodically asks EFO if it’s done processing. Two environment variables,
EFO_POLLING_INTERVAL
andEFO_POLLING_MAX_DURATION
, control how long our back-end waits between requests and how long polling will last before considering the task “failed” (values measured in seconds).These environment variables currently have placeholder values (30 seconds and 300 seconds, respectively), and we need to work with the FEC to determine the best values for DEV, STAGE, and TEST going forward. Once we have those numbers pinned down, we can simply update our manifest files to implement them.
QA Notes
There will be no visible changes to behavior
DEV Notes
null
Design
null
See full ticket and images here: FECFILE-1699