Hi,
I have created custom lambda which recently did work. For some reason the lambda did stop working. For testing purposes I have created a slimmer version of it, which does not work as well!
Here’s the lambda
export const createTest = async ({ args, graphql, authHeader }) => {
const test = await graphql(
`
mutation add {
addTest(input: { name: "hello world" }) {
numUids
}
}
`
);
return { result: JSON.stringify(test) }
}
The type Test is simply:
type Test {
id: ID!
name: String
}
I have tested the mutation on the cloud which works as intended. Unfortunately the exact same mutation in the lambda does not work. I know that the mutation is getting executed - I have tested to submit an Integer instead of a String for name
- here I receive an error message that the field has the wrong type. If the name
is a string as above then I get the result data.addTest: { null }
.
Usually this means that something with the access is off but I have set all fields and the lambda to *publicly queryable".
Is there a cache or something I can clear? This is driving me mad, I’ve already spent 2 days on this issue!