SUPPORT

Get help with Dynodoc.

Where to read, how to report a problem and what to expect back. Dynodoc is in testing, so this page also says plainly what is not available yet.



REPORT A PROBLEM

Report a bug or ask a question.

GitHub Issues is the channel for bug reports and questions today. Issues are public, so write each one as if a stranger will read it.

Include

  • The page or editor involved, and its version (for example, Word for Windows).
  • What you expected and what happened instead.
  • Steps to reproduce, using a small copy of a file with nothing sensitive in it.
  • Screenshots with any private content hidden.

Leave out

  • Connection keys, pairing codes, passwords and sign-in links.
  • Document contents you would not publish.
  • Security vulnerabilities. Report those privately, as described below.

SECURITY

Found a vulnerability?

Do not open a public issue. The security page explains what to report and how.


CONTACT AND STATUS

What exists today, and what does not.

These are stated as they are so that nobody waits on a channel that is not there.

Support email
Awaiting confirmation

No support address has been decided yet. It will be listed here once the operator confirms one. Until then, use GitHub Issues.

Service status
No status page

There is no live status page. If you cannot reach the service, report it on GitHub Issues with the time and the page you were using.

Response times
Not promised

Dynodoc is in testing. Reports are read as capacity allows, with no response-time commitment and no service-level agreement.

Operator details
Awaiting confirmation

The legal operator, contact details and jurisdiction are not final. The privacy policy and terms remain drafts until they are.


ADD-IN HELP

Common questions about the editor add-ins.

The add-in says my editor is not supported. What now?

The add-ins need Word with WordApi 1.3, Excel with ExcelApi 1.13 or PowerPoint with PowerPointApi 1.4. PowerPoint 2021 and earlier do not have PowerPointApi 1.4; use a current Microsoft 365 build or Office 2024. Google add-ins run in a desktop browser, not in the mobile apps. In any unsupported editor you can still push an edited file for review from Projects.

My connection stopped working.

A connection reaches one file and expires seven days after you approve it. It also stops if someone revokes it under Sync & connections. Choose Sign in to Dynodoc again in the pane or sidebar and approve the file. Office panes hold the connection in memory, so reopening the pane needs a new sign-in.

Capture did not record my edit.

Capture runs only while the pane or sidebar is open and capture is switched on. It records edits to existing paragraph text, cell values, formula source, date-only values and shape text. New, deleted or moved content and formatting are not captured; use an edited-file push for those.

Google says storage is full and capture stopped.

Google keeps about 500 KB of saved add-on data per user and script, shared by every file you connect, and each file queue is capped at 100 KB. When the store is full the sidebar stops capture and keeps your previous saved queue. Use Export local provenance to keep a copy of your queue. The add-on has no clear action today.

I renamed or copied the file and the connection stopped.

Word rechecks the saved file address. After Save As or a rename the active connection stops and its queue stays exportable. Reopen the pane in the saved copy and choose the exported recovery file before reconnecting.

My file is rejected as too large.

During testing an original file can be at most 3 MB (3,000,000 bytes). Workbook imports are also limited to 3,000 rows and 100 columns. Split or trim the file and try again.