aws-amplify / aws-amplify/amplify-cli

amplify update notifications error: pushTransform already has a running timer

Open
#12,734 10 comments 0 reactions 0 assignees View on GitHub
bug notifications p2
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### How did you install the Amplify CLI?

npm

### If applicable, what version of Node.js are you using?

v16.15.1

### Amplify CLI Version

12.0.3

### What operating system are you using?

Mac

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

### Describe the bug

I ran 'amplify update notifications' and get the follow error/resolution message:

"
Edit your schema at /.../schema.graphql or place .graphql files in a directory at /...schema
Deployment state saved successfully.

GraphQL transformer version: 2

🛑 pushTransform already has a running timer

Resolution: **Please report this issue at https://github.com/aws-amplify/amplify-cli/issues** and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

"

### Expected behavior

I expect 'notifications' category to be updated (even though I have not made any manual change). I also expect to be able to run 'amplify pull --appId XXX --envName staging' and 'amplify push' successfully. Currently I'm getting "Could not initialize categories for 'staging': Cannot read properties of undefined (reading 'Soar4JrbB')" when I run 'amplify pull'

### Reproduction steps

1. Run 'amplify update notifications' in Android Studio terminal window

### Project Identifier

adf24a36f9a97bc1518d1dfa8861c7ae

### Log output

```
# Put your logs below this line

```

"
⠧ Building resource api/Soar✅ GraphQL schema compiled successfully.

Edit your schema at /.../schema.graphql or place .graphql files in a directory at /...schema
Deployment state saved successfully.

GraphQL transformer version: 2

🛑 pushTransform already has a running timer

Resolution: **Please report this issue at https://github.com/aws-amplify/amplify-cli/issues** and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: c774bd85-f540-4c40-b2db-a822f7201ecf

✅ Report saved: /...zip

✔ Done

"

### Additional information

_No response_

### Before submitting, please confirm:

- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure with Amplify CLI 12.0.3, Node.js v16.15.1, and the reported `amplify update notifications` command, then compare its behavior with `amplify pull` and `amplify push`. Review the referenced `schema.graphql` location and the GraphQL transformer output around `pushTransform already has a running timer`. Done means notifications update and subsequent pull and push complete successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, graphql, node.js, typescript
Domain
api, cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.