Prisma

but yes it does also appear to be CORS issues as well

when you're not having those cors issues, can you then run queries in the console?

and then end up with a `TypeError: Failed to fetch` in the console

preflight check failing : `<https://nib2v8z803.execute-api.eu-west-1.amazonaws.com/Prod>`

Anyway, I get the same errors as <@U4BF8DHB4>

thanks everyone. We'll get this sorted as soon as possible but given that it's 2am it might take a few more hours 

<@U0RQY0KK5> rough! Thanks for tracking it - let us know if you need anything

Just stopped by to see what was up with your amazing service and why my console was acting strange (and throwing CORS errors) -- looks like that is a known issue so i'll just be patient and join fans here on the side ready to assist any way we can.

Who do I gotta send beer to for when this all gets cleared up? good luck! :four_leaf_clover:

Guess I'll have to play mass effect now...

Hello does anybody has issues with connection to their graph.cool api?

good luck everyone :slightly_smiling_face:

I receive  503 Service Temporarily Unavailable

<@U42NTKX2T> Please read the previous messages in this channel

ah I see. so is the cors problem solved? still working on it?

Last message I heard was that it is 2AM there, may take a few hours.

is this the first time gcool has been down for so long before?

just wondering to get an idea on reliability

<@U4B7XQW90> Yeah, I’ve been developing since beginning of this year and this has never happened. It’s been 100% reliable thus far, and I’ll continue to use this platform. This is probably a one-time migration error.

This is the first time I've been impacted in three weeks - and I've been using it a lot.

I've been developing with it for ~45 days now, and this is the first time I've been impacted by downtime

first time for me, using it since January

<@U4VMSDF1Q> yes I am using apollo with vue-apollo and NUXT

but don’t use vue-supply for vuex, did not really see a need for that

Oh good...it's not my code that's broke :joy: 

is it possible to use query variables in a filter?

<@U42DA0Q66> I think you can do it with a fat arrow on the constructor in a way similar to how I am using a route on the URL (/product/id) to filter this query:  const ProductOrderPageWithData = graphql(FeedQuery, {
  options: (props) =&gt; ({ variables: { what: props.params.productId } }),
})(ProductOrderPage) - does that help?

I'm wondering if I pass an array in to `variables: {allowableStatuses}` if that array will be used correctly within the query

I'm guessing probably, but since graphcool is down right now I can't test it :slightly_smiling_face:

haha, that's why I was taking a swing at an answer, since i'm patiently hoping it will re-appear myself :slightly_smiling_face:

```
query ($userId: ID!, $allowableStatuses: [EVENT_STATUS!]!){
  User(id: $userId) {
    team {
      events(filter: {
        status_in: $allowableStatuses
       }) {
        id,
        title,
        locationName,
        eventDateTime,
      }
    }
  } 
}
```

you can also define a variable for the whole filter object

`filter: {status_in: $allowableStatuses}`

Thanks everyone for your patience, we're looking into this right now :slightly_smiling_face: 