PulpHub help / PulpHub

Help article

Troubleshooting access saves and unavailable features

Start by checking the page message and whether your account is signed in, verified and on the required plan. Keep a local copy of unsaved text before reloading. Common problems

Start by checking the page message and whether your account is signed in, verified and on the required plan. Keep a local copy of unsaved text before reloading.

Common problems

  • An upgrade message means the action requires a higher plan; new book creation requires Studio.
  • A file rejection can mean an unsupported type, a file over 5 MB or excessive DOCX expansion.
  • A provider-unavailable message can affect a specific AI tool even while other generation tools work.
  • A queued or failed generation job needs status review before another job is started.
  • A checkout return can arrive before payment confirmation updates your plan.
  • Social connection and posting controls remain unavailable while setup is paused.

Report a problem

Record the page path, time, action, visible error and request identifier if shown. Include the book or job identifier when relevant. Do not send passwords, API keys, recovery links, payment details or private manuscript text.

If the application offers a reload recovery screen after an update, save any recoverable work locally and use that reload control. A stale browser tab should not be used to repeat an uncertain external action.

Still need help?

Send a request to a person. Include the application, what you tried and what happened. Do not include sensitive information in the first message.

Contact support