# The error `push.after-publish`

**environment**: something the run needs is missing or different where it runs (a package, a file, a device, the network): the error names what to install, fetch or attach.

Where MIME gives it, with what its message says happened and what its action says to do (`{…}` is filled in from the experiment):

- in `mime/push/_publish.py`:
  - what happened: `the record {…} on {…} does not read as published yet, so push recorded nothing and wrote no lock`
  - what to do: `run the same command again in a moment, 'mime push <folder> --to {…} --publish': it reads the record first`
- in `mime/push/_publish.py`:
  - what happened: `the record {…} on {…} is published, and read back it differs from what push sent: {…}; so push did not write its lock into the folder`
  - what to do: `look at the record, {…}; run 'mime push <folder> --to {…} --publish' again, which checks it again and publishes nothing; if the folder changed since the draft, 'mime push <folder> --to {…}' makes its next version`

Reading an error and reaching its full traceback: [reading an error](../reading_errors.md). Every code: [the index](index.md).