Known issues and common questions

The things we already know about, so you are not the one to find them, and the questions they tend to produce.

A few things we already know about. None of them touches the accuracy of a figure you enter yourself: budgets, draws, pay applications and exports add up correctly, and that is the part that has been tested hardest.

If what you have hit is not on this page, write to [email protected]. The Help menu inside the app opens that same message for you with the workspace, the screen and the build already filled in, which is most of what makes a report answerable. Use it from the screen that went wrong if you can.

A weather day is a whole day

Everything a weather day feeds is built and running. The seven-day forecast reads on every schedule lane and flags the groups your workspace says stop for rain; logged weather days are excluded from every stoppage source's idle count; and a contract's weather allowance absorbs what it covers, with the outside date extended only by the rest. A day is logged from the weather page by whoever holds schedule access at edit. What the log cannot hold is a partial day: a morning lost to rain is either a day on the log or not on it.

Two markers on the same date sit on top of each other

On a project's schedule timeline, two things falling on the same date overlap exactly, and the one underneath cannot be clicked. If you know something is there on a busy date and cannot reach it, move one of the two and the other comes back.

Forwarding email into a project depends on the deployment

Every project has an intake address. Whether mail sent to one reaches PadFlow is a setting on the deployment you are using rather than something you can switch on from inside the app, so ask whoever runs yours. Where it is off, the Outlook add-in is the way to bring a message and its attachments into a document register, and it is worth setting up on day one if that path matters to you.

A funded draw cannot be marked paid without an accounting connection

Marking a draw's bills as paid reads from a connected accounting company file. Until that connection exists the draw can be funded and cannot be marked paid. Everything else about the draw, including the package the lender receives, works without it.

Shipping an update does not interrupt the app

An update is built and started beside the version serving you, and it takes no traffic at all until it has answered a health check with the build it was just given. Only then does the front door start sending new requests to it; connections already open are given time to finish, and the old version is stopped after that. A build that fails, or that comes up and cannot answer for itself, never receives a request, and the version you are using is not restarted, rebuilt or touched.

A deploy also waits for the app to be idle before it starts, so an update is not applied underneath somebody mid-draw. If a page does fail while we are shipping, that is a bug rather than the expected cost of an update, and [email protected] is the address to tell.

A screen says not found when I expected to be told I cannot see it

A route you do not hold the level for renders the not-found page rather than a refusal that names the missing level. That is deliberate: an area a role cannot open must not confirm what is behind it, so the same page answers for a project that was deleted, for a link into a workspace you are not a member of, and for one your access does not cover.

The page names all three, and access is the third: "your role may not include this area", with the advice to ask your workspace admin. Nothing has gone wrong with your session. The roles page explains what each level means, and an administrator in your workspace can change it.

A figure reads as a dash instead of a number

That is money redaction working. At view_redacted on money you get the rows, the codes and the status and no amounts, so progress can be tracked without price being shown. A dash means withheld. It never means zero, and no page sums a withheld figure into a total.

The workspace takes several seconds to open

The portfolio overview counts across every project on every load. A workspace holding several hundred projects takes a few seconds to draw. Opening a single project is not affected.