BUG "The security token included in the request is invalid. (Service: DynamoDb, Status Code: 400, Request ID…"

Describe the bug I am getting this error intermittently when loading data using graphql - the code is running a loop and seems to randomly fails with this error.

Amplify CLI Version 4:30.0

To Reproduce Not sure if this is reproducible

Expected behavior I wouldn’t expect random failure when processing data items in a loop.

Desktop (please complete the following information):

• OS: macOS10.15.7
• Node Version: v12.18.1

Additional context This seems to be a new issue that has started occurring

Sample Code

export const loadSessionTypeCodes = async () => {

  const results = await API.graphql({ query: customQueries.listSessionTypes });
  // console.log("results.data.listSessionTypes.items: " + results.data.listSessionTypes.items.length)
  console.log("listSessionTypes", results.data.listSessionTypes.items)

  if (results.data.listSessionTypes.items.length > 0) {
    return results.data.listSessionTypes.items.sort(function (a, b) { return a.name > b.name })
  }

  for (const item of sCodesInput) {
    console.log("item: " + item.name)
    try {
      const newCodeResult = await API.graphql({
        query: mutations.createSessionType, variables: {
          input: { name: item.name }
        }
      });

      const newCode = newCodeResult.data.createSessionType

      // Load activity types
      for (const subitem of item.activityTypes) {
        console.log("subitem: " + subitem.name)
        console.log("newSessionType.id: " + newCode.id)
        try {
          const newSubcode = await API.graphql({
            query: mutations.createActivityType, variables: {
              input: { name: subitem.name, activityTypeSessionTypeId: newCode.id }
            }
          });
        } catch (err) {
          console.log("error creating ActivityType codes", err)
        }

      }

      // Load modes
      for (const subitem of item.modes) {
        // console.log("subitem: " + subitem.name)
        // console.log("newSessionType.id: " + newCode.id)
        try {
          const newSubcode = await API.graphql({
            query: mutations.createMode, variables: {
              input: { name: subitem.name, modeSessionTypeId: newCode.id }
            }
          });
        } catch (err) {
          console.log("error creating Modes codes", err)
        }

      }

    } catch (err) {
      console.log("error creating SessionType codes", err)
    }

  }

  const listresults = await API.graphql({ query: customQueries.listSessionTypes });
  // console.log("listresults.data.listSessionTypes.items")
  // console.log(listresults.data.listSessionTypes.items)
  return listresults.data.listSessionTypes.items.sort(function (a, b) { return a.name > b.name })
}

** Additional information ** If I change the code to use graphqlOperation this error seems to go away - is there an explanation for this ?

export const loadSessionTypeCodes = async () => {

  const results = await API.graphql({ query: customQueries.listSessionTypes });
  // console.log("results.data.listSessionTypes.items: " + results.data.listSessionTypes.items.length)
  console.log("listSessionTypes", results.data.listSessionTypes.items)

  if (results.data.listSessionTypes.items.length > 0) {
    return results.data.listSessionTypes.items.sort(function (a, b) { return a.name > b.name })
  }

  for (const item of sCodesInput) {
    console.log("item: " + item.name)
    try {
      const newCodeResult = await API.graphql(graphqlOperation(mutations.createSessionType, {
          input: { name: item.name }
        }));

      const newCode = newCodeResult.data.createSessionType

      // Load activity types
      for (const subitem of item.activityTypes) {
        console.log("subitem: " + subitem.name)
        console.log("newSessionType.id: " + newCode.id)
        try {
          const newSubcode = await API.graphql(graphqlOperation(mutations.createActivityType, {
              input: { name: subitem.name, activityTypeSessionTypeId: newCode.id }
            }
          ));
        } catch (err) {
          console.log("error creating ActivityType codes", err)
        }

      }

      // Load modes
      for (const subitem of item.modes) {
        // console.log("subitem: " + subitem.name)
        // console.log("newSessionType.id: " + newCode.id)
        try {
          const newSubcode = await API.graphql(graphqlOperation(mutations.createMode, {
              input: { name: subitem.name, modeSessionTypeId: newCode.id }
            }
          ));
        } catch (err) {
          console.log("error creating Modes codes", err)
        }

      }

    } catch (err) {
      console.log("error creating SessionType codes", err)
    }

  }

  const listresults = await API.graphql({ query: customQueries.listSessionTypes });
  // console.log("listresults.data.listSessionTypes.items")
  // console.log(listresults.data.listSessionTypes.items)
  return listresults.data.listSessionTypes.items.sort(function (a, b) { return a.name > b.name })
}

[kaxax]

For me issue started when I delete and recreate some table on amplify schema several times. after a few minutes issue disappeared on its own. I think appsync was trying to connect a new table with old (deleted same-named table) credentials. after few minutes it’s started to use new credentials and the issue disappeared. does anyone experience this issue for more than several minutes?

Amplify CLI Version 4.44.0

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.