Matthew Suan
Matthew Suan
this might be an issue on varnish caching and you can just remove varnish to fix it.. but if you want to still use varnish, just disable varnish cache on...
hi @JamiesonRoberts have you found a way around this?
for anyone stumbling into this, you need to access acf field via the field type accessor method. instead of ``` $post->acf->field_name ``` you can do it via ``` $post->acf->{fieldType}('field_name') so...
I dug deeper and only `action-type` notification is supported. `User` and `Action Performed` types are not implemented.
@evoaran we are experiencing this issue as well. It fixes itself i think when lambda spawn another micro container instance.
I went and checked logs and these same errors happen during occasional timeouts (28 secs) as well though I expect timeouts from time to time with my application. I think...
@mnapoli I wanted to access the `deadlineMs` value so I can pre-emptively do something before a lambda timeout occurs. Do you think we can add support to this?
Inside `LaravelSqsHandler.handleSqs` we have access to `Context` object but then it was never used. I think we can set $_SERVER['LAMBDA_INVOCATION_CONTEXT'] from there same way we did with the `FpmHandler`? Or...