Troubleshooting: access, companies and setup

Core module Odoo Enterprise: Barcode app Odoo Enterprise: Quality app 3PL add-on For: Administrator, Compliance manager, Warehouse staff, Sales and purchasing Checked on 18.0.0.2.0, 18.0.1.0.0

What to do when a message names a role, an access right, another company or a switched-off feature, or when an email or a scheduled job seems missing. These conditions can happen in every guide, so each one has a single entry here and the other troubleshooting pages link to it. Entries are ordered from the most frequent. Who has which right is in Roles and permissions.

Error: "Only DSCSA users can ..."

What you see: an Access Error (or Invalid Operation) dialog, or an error line in an import, with one of these texts:

Only DSCSA users can scan DSCSA serials onto a transfer.
Only DSCSA users can remove scanned DSCSA packages from a transfer.
Only DSCSA users can import or cancel supplier EPCIS files.
Only DSCSA users can record a Transaction Statement.
Only DSCSA users can set or change the DSCSA role of PARTNER: the role decides which licenses make the partner an authorized trading partner.
Only DSCSA users can set or change the small-dispenser exemption of PARTNER: it lets the customer receive lot-level instead of package-level transaction data.
Only DSCSA users can apply a count that lowers the stock of a DSCSA product: the serials of the missing units must be recorded in the package ledger.
Only DSCSA users can scrap PRODUCT: the serials of the scrapped units must be recorded in the package ledger.
Only DSCSA users can do this on a trace request.
Only DSCSA users can change the DSCSA investigation of a quality alert.
Only DSCSA users can change the investigated owner or split an investigation.
Only DSCSA users can record the supplier's data or the owner's confirmation.
Only DSCSA users send an owner's documents.
Only DSCSA users can send owner notices.
Only DSCSA users can list the consignees of a recall.

When: a person without the Rx Tracking User right does DSCSA work. The buttons are hidden from them, so they meet the message where Odoo's own screens let them act: an Inventory user who applies a count or scraps a DSCSA product, a Quality user who edits an investigation in the Quality app, a contact editor who imports a partner's DSCSA Role, or an import or script. For example, a script run by the salesperson Jordan Patel that sets Brightside Medical Supply's role gets "Only DSCSA users can set or change the DSCSA role of Brightside Medical Supply Inc.: …".

Cause: the action changes the package ledger, a trading partner's authorization or a DSCSA record, and needs the Rx Tracking User right (or Manager, which includes it). Nothing was saved: the check runs before anything is written, and an import is refused as a whole.

Remedy: a resolution.

1. Hand the task to a colleague who is an Rx Tracking User, or ask an administrator to give you the right: Give staff the right Rx Tracking access.
2. Reload the page (the new right shows after a reload or a new sign-in), then repeat the action.

Entries for specific cases: a count that lowers the stock, a scrap, trace requests, owner data and confirmations.

Known issue

Known issue (PF-W04-02): a person without a right to edit contacts who sets a partner's DSCSA Role or Small Business Dispenser gets this message, but the Rx Tracking User right alone doesn't let them edit the contact: they also need Contact Creation (PF-W03-02). Give both, or hand the task to someone who has both.

Who can fix it: Administrator (Administration: Settings) gives the right; any Rx Tracking User can do the task instead.

Error: "Only a DSCSA manager can ..."

What you see: an Access Error dialog, or an error line in an import. For example, when the warehouse user Sam Rivera applies a count that raises the stock of a lot in Inventory ‣ Operations ‣ Physical Inventory:

The other texts of this family start with "Only a DSCSA manager can", "Only DSCSA managers can", "Only DSCSA managers" or "Only DSCSA managers with access to the Settings can":

The message is about	Distinctive part
quarantine	"… can quarantine or release a lot."
returns	"… can verify a returned package for resale.", "… can verify or reject returned packages.", "… can mark or unmark a return to the supplier as non-saleable: …"
stock	"… can apply a count that raises the stock of a DSCSA product: …", "… can register an opening balance in the package ledger."
master data	"… can change whether PRODUCT is a DSCSA product: …", "… can mark a license verified."
receiving	"… can reopen a discrepancy."
records	"… can place or release a legal hold.", "… can export the package ledger and license register.", "… can manage the S3 archive queue.", "… with access to the Settings can set the S3 archive secret key."
trace requests	"Only DSCSA managers can do this on a trace request." (cancelling)
3PL	"… grant or revoke the owner portal.", "… publish an owner's documents to its buyer.", "… record an owner's authorization to issue its documents.", "… can export an owner's records.", "… can mark a facility event reported.", "… can mark an FDA annual report submitted.", "… can mark a jurisdiction verified.", "… can change the third-party logistics (3PL) settings.", "… can record a receipt as custody …", "… can validate a title transfer.", "… can link the invoice of a done title transfer."

When: an Rx Tracking User (or a person without any Rx Tracking right) tries a manager action. Most manager buttons are hidden from users, so the message usually comes from Odoo's own screens (a count in Physical Inventory), an import, a script or a link.

Cause: the action is reserved to the Rx Tracking Manager right. Your procedure decides who holds it; the software requires it. Nothing was saved.

Remedy: a resolution.

1. Ask an Rx Tracking Manager to do it, or ask an administrator to give you the Manager right (Give staff the right Rx Tracking access).
2. For the S3 secret key and the 3PL settings, the person also needs Administration: Settings.
3. Repeat the action after a reload.

Entries for specific cases: a count that raises the stock, the opening balance, legal holds, retention exports, reopening a discrepancy, the owner portal, title transfers. "Returned DSCSA units in … are waiting for verification. Only a DSCSA manager can release them …" is a different condition: see Returned units waiting for verification.

Who can fix it: Rx Tracking Manager does the task; Administrator (Administration: Settings) gives the right.

Error: "You are not allowed to access ... records"

What you see: Odoo's Access Error dialog:

You are not allowed to ACTION 'RECORD-TYPE' (MODEL) records.

This operation is allowed for the following groups:
	- GROUP
	- GROUP

Contact your administrator to request access if necessary.

ACTION is access, modify, create or delete. Instead of the list of groups, the second part may say "No group currently allows this operation." For example:

• a salesperson who opens a license link: "You are not allowed to access 'Trading Partner License' (dscsa.license) records." allowed for "Rx Tracking/Manager" and "Rx Tracking/User";
• an Rx Tracking User who tries to create a license: "You are not allowed to create 'Trading Partner License' (dscsa.license) records." allowed for "Rx Tracking/Manager";
• an Rx Tracking User who opens a retention export link: "… 'DSCSA Retention Export' (dscsa.retention.export) …" allowed for "Rx Tracking/Manager";
• anyone, the administrator included, who deletes a posted DSCSA document or a package: "You are not allowed to delete 'DSCSA Transaction Document' (dscsa.document) records. No group currently allows this operation."

When: opening a link, an import, or a button that reaches a kind of record the person's rights don't cover. It also appears on Odoo's own screens when they read DSCSA records in the background (see the Known issue below).

Cause: the person has none of the groups listed. When the message says "No group currently allows this operation", nobody may do it: the record is kept by design (Error: "... can't be changed" or "... can't be deleted" on a kept record).

Remedy: a resolution.

1. Read the groups the message lists: "Rx Tracking/User" or "Rx Tracking/Manager" is the Rx Tracking level on the user form; "Inventory/User" is the Inventory level; "Extra Rights/Contact Creation" or "Extra Rights/Product Creation" are shown on the user form in developer mode.
2. Ask an administrator to give the person one of them (Give staff the right Rx Tracking access), or hand the task to someone who has it.
3. Repeat the action after a reload.

Known issue

Known issue (PF-W20-05): a Purchase User without an Inventory or Rx Tracking right who cancels a confirmed purchase order gets "You are not allowed to access 'DSCSA Package' (dscsa.package) records. …", even for an order without DSCSA products. Ask someone with Inventory User to cancel it.

Who can fix it: Administrator (Administration: Settings).

Error: "Uh-oh! Looks like you have stumbled upon some top-secret records"

What you see: Odoo's Access Error dialog:

Uh-oh! Looks like you have stumbled upon some top-secret records.

Sorry, USER (id=ID) doesn't have 'read' access to:
- RECORD-TYPE (MODEL)

If you really, really need access, perhaps you can win over your friendly administrator with a batch of freshly baked cookies.

This seems to be a multi-company issue, but you do not have access to the proper company to access the record anyhow.

The last line appears only when the record belongs to a company the person can't use. For example, Jamie Ortiz, who works only for Demo Rx Distribution East LLC, opening a link to a document of Demo Rx Distribution LLC gets it for "DSCSA Transaction Document (dscsa.document)".

When: opening a link or a record of another company, or (customer and owner portal users) a record of another customer or owner through the backend. On the portal itself, a record the person may not read shows "Error 404" instead.

Cause: every DSCSA record belongs to one company, and a person sees the records of the companies selected in the company switcher, among the companies they are allowed to use. A person allowed to use the other company doesn't get this error: Odoo opens the record and adds its company to the selection.

Remedy: a resolution.

1. If the record belongs to another of your companies, ask an administrator to add that company to your Allowed Companies (Set up and work in a multi-company database).
2. Otherwise the record isn't meant for you: ask a colleague of that company.

Who can fix it: Administrator (Administration: Settings).

Error: "... belongs to another company"

What you see: one of these:

Trace request DSCSA/TR/YYYY/NNNNN only covers the records of COMPANY; these belong to another company: RECORDS.
Instruction INSTRUCTION belongs to another company.
The warehouse belongs to another company.
LABEL belongs to another company.
Licence LICENSE names the facility FACILITY, which belongs to COMPANY: only that company's own licences are recorded per facility.
A package with this GTIN and serial number is already registered.
A trace request number must be unique per company.

When: a record of one company is used on a record of another: a trace request whose query names another company's records, an owner instruction or a warehouse of another company on a title transfer (3PL add-on), a facility license recorded for another company's warehouse (3PL add-on). The last two lines come from imports and scripts only.

Cause: DSCSA records don't cross companies: each company keeps its own package ledger, documents, trace requests and 3PL records. The same unit can be registered once in each company's ledger, but only once per company.

Remedy: a resolution. Select the right company in the company switcher, then pick records of that company only. The entries that explain each case: trace requests, owner instructions, title transfers, facility licenses. To move stock from one of your companies to another, see Move DSCSA stock between two of our companies.

Who can fix it: the person doing the task (Rx Tracking User or Manager).

Error: "... can't be changed" or "... can't be deleted" on a kept record

What you see: a message saying a DSCSA record is posted, done, verified or kept, for example:

DSCSA document DSCSA/OUT/2026/00001 is posted and can't be changed (fields: date).
DSCSA packages change only through the package ledger's own operations (scans, receipts, deliveries, returns, scrap, inventory counts, quarantine), not directly. Refused change of: Serial Number.
PA State license DEMO-PA-WHL-44120 cannot be deleted: verified licenses are verification evidence and must be kept for six years. Archive them instead.

or Odoo's "You are not allowed to delete '…' records. No group currently allows this operation."

When: editing or deleting a posted document, a package, a verified license, a done DSCSA operation, a trace request's log, a stored file, a supplier file or a 3PL record that is kept; mostly through an import, a script or a record's ⚙ (Actions) menu.

Cause: these records are the DSCSA history, and nobody may change or delete them, the administrator included. Background: DSCSA sets a record-keeping period for transaction data (FD&C Act § 582, record-keeping provisions; see Compliance background). The retention settings and what each record keeps are described on Records that are kept.

Remedy: a workaround: record the correction as a new record instead of changing the old one. The entry for each kind of record says how: packages, stored files, lots in posted documents, verified licenses and their deletion, supplier files and discrepancies, done lines, owner profiles, and the 3PL records on 3PL records that are kept.

Who can fix it: nobody can change the record; the person who made the mistake records the correction.

Error: "... not an authorized trading partner" when you have no Rx Tracking right

What you see: an Invalid Operation dialog when you confirm a quotation, a request for quotation or a purchase order, or validate a transfer, for example as the salesperson Jordan Patel:

S00026 can't be confirmed: it contains DSCSA products ([DEMO-DPZ-20] Demoprazole 20 mg Delayed-Release Capsules, 30 count).
Lakeview Apothecary (dispenser) has no valid state license: license DEMO-CA-PHY-61177 expired on 2026-09-12.

Selecting Confirm RFQ in the ⚙ (Actions) menu of several requests for quotation lists one such paragraph per refused order, and confirms none of them.

When: you sell to, buy from, ship to or receive from a partner that is not an authorized trading partner today, and the order or transfer has DSCSA products. Products that are not DSCSA products are never named and never cause the refusal: an order with only such products confirms.

Cause: the partner's DSCSA role or licenses don't make it an authorized trading partner (the reason line says which). You can't see the partner's DSCSA tab without an Rx Tracking right (Known issue PF-A01-09), and you can't fix the partner yourself. Background: DSCSA sets rules for who is an authorized trading partner (FD&C Act § 582(c)(3), § 581(2); see Compliance background).

Remedy: a resolution.

1. Send the reason line to your compliance manager. The fix for each reason is in Error: "… can't be confirmed: it contains DSCSA products …".
2. When they tell you the partner is fixed, repeat the action. The order stayed as it was (a quotation stays a Quotation).
3. If the order can go ahead without the DSCSA products, remove their lines and confirm the rest.

Who can fix it: Rx Tracking Manager (licenses); Rx Tracking User with a right to edit contacts (the DSCSA Role).

Error: "Third-party logistics (3PL) is off for ..."

What you see: one of these (3PL add-on):

Third-party logistics (3PL) is off for COMPANY: title transfers need it.
Third-party logistics is off for COMPANY: an opening balance can't be held for an owner.
3PL is off for COMPANY.
Third-party logistics is off for COMPANY: there is no owner to split for.
Turn on third-party logistics (Inventory settings, DSCSA 3PL) for COMPANY before creating owner profiles.
Turn on third-party logistics for COMPANY before re-activating OWNER.

A title purchase order lists "third-party logistics (3PL) is off for the company." among its reasons.

When: a 3PL action (owner profiles, title transfers, owner opening balances, recall consignees, splitting an investigation per owner) in a company where 3PL is switched off, often because the wrong company is selected in the company switcher.

Cause: the 3PL add-on is installed, but its switch is off for the selected company. Installing the add-on doesn't switch it on, and each company has its own switch.

Remedy: a resolution.

1. Check the company switcher: select the company that holds owners' stock.
2. If it is the right company, ask an administrator to switch 3PL on: Turn on third-party logistics for a company.
3. Repeat the action.

More detail: owner profiles, title transfers.

Who can fix it: Administrator (Administration: Settings) who is also Rx Tracking Manager.

Error: "DSCSA owner isolation (3PL): ..."

What you see: an Invalid Operation dialog whose first line is "DSCSA owner isolation (3PL):", followed by one line per problem (3PL add-on).

When: Mark as Todo, Save, Scan Serials ‣ Register or Validate on a transfer that moves units held for an owner, in the backend or in the Barcode app.

Cause: an owner's DSCSA units serve only that owner's orders, a transfer is for one owner (or for your own stock), and units never change owner except through a title transfer.

Remedy: a resolution. Find the line in the table of Error: "DSCSA owner isolation (3PL): …" and follow the entry it names.

Who can fix it: Rx Tracking User or Manager for scans and transfers; Rx Tracking Manager for owner profiles.

Error: "DSCSA products can't be consumed or produced here ..."

What you see: one of these:

DSCSA products can't be consumed or produced here (MOVES): the package ledger can't record which serialized units are used. Manufacturing, repair and kits don't handle DSCSA products; to destroy units, scrap them with their serials.
PRODUCTS: DSCSA products are received from or shipped to a trading partner only on a transfer (receipt, delivery or return), where the trading partner and the serials are checked.
DSCSA stock (PRODUCTS) can only be relocated to an internal location of its company, not to LOCATION. Use a transfer, a scrap or an inventory count.

When: a manufacturing, repair or kit order uses a DSCSA product; a script moves DSCSA stock to or from a partner without a transfer; an Inventory Administrator changes the Location of a lot on its form to a location outside the company's stock (Odoo moves the stock at once, without a transfer).

Cause: the package ledger records every unit's moves, so DSCSA stock leaves or enters the company only on a receipt, a delivery, a return or a scrap, where the trading partner and the serials are checked. The full list of these rules is on What is checked where.

Remedy: a workaround: use the operation the message names. To destroy units, scrap them with their serials; to move stock between shelves, use an internal transfer; to correct quantities, count them. See also Relocate is refused. A Point of Sale order of a DSCSA product gives no message: its delivery stays open until an Rx Tracking user scans the serials and validates it in Inventory.

Who can fix it: Rx Tracking User (transfers, scraps and counts that lower stock); Rx Tracking Manager (counts that raise stock).

A non-DSCSA product is refused

What you see: an order, a transfer or a count of a product that is not a DSCSA product is refused, or asks for something DSCSA products need.

When: any operation.

Cause: the Rx Tracking checks never refuse a product whose DSCSA Product box is clear: they name only DSCSA products, and an order or transfer with only other products goes through as in standard Odoo. So the refusal comes from something else:

• the product is a DSCSA product after all (its DSCSA tab has DSCSA Product ticked);
• Odoo's own rules, for example "You need to supply a Lot/Serial number for products …" for a lot-tracked product (Error: "You need to supply a Lot/Serial number …");
• with 3PL switched on, the company's Owner isolation for non-DSCSA products policy extends the owner rules to other products (Choose the company's 3PL policies);
• the Known issue PF-W20-05: cancelling a confirmed purchase order as a Purchase User without Inventory rights (Error: "You are not allowed to access ... records").

Remedy: a resolution.

1. Open the product (Inventory ‣ Products ‣ Products) and check its DSCSA tab. If DSCSA Product is ticked by mistake, ask an Rx Tracking Manager to clear it (Stop treating a product as DSCSA).
2. Otherwise follow the entry for the message you see.
3. If an Rx Tracking message names a product that is not a DSCSA product, report it to your implementer: it is a product defect.

Who can fix it: Rx Tracking Manager (the product flag); Administrator (Administration: Settings) for Odoo's own settings.

The Rx Tracking modules aren't in Apps

What you see: in Apps, a search for Rx Tracking shows "No module found!" and "You should try other search criteria.", or fewer than six Rx Tracking cards.

When: installing the modules (Install Rx Tracking (DSCSA), steps 4–5).

Cause: one of these:

• the Apps filter is still in the search bar: it shows applications only, and no Rx Tracking module is an application;
• the module folders were copied to the server after the database was created, and the Apps list wasn't updated since;
• the folders aren't on the server's addons path, or Odoo wasn't restarted after they were copied.

Remedy: a resolution.

1. Select the × on the Apps facet in the search bar and search again (Install Rx Tracking (DSCSA), step 4).
2. If the cards still don't appear, update the Apps list: If the modules aren't listed: update the Apps list.
3. If they still don't appear, ask whoever runs the server to check the folders and the addons path, and to restart Odoo: Put the modules on the server.

Who can fix it: Administrator (Administration: Settings); the addons path: whoever runs the server.

There is no Sales app after installing Rx Tracking

What you see: after installing Rx Tracking (DSCSA), the home screen has Inventory, Purchase and Invoicing, but no Sales, and sales staff can't create quotations.

When: after Install Rx Tracking (DSCSA) on a database without Odoo's Sales app.

Cause: the core module installs Odoo's sales engine, which it needs, but not the Sales app (Known issue PF-T02-01).

Remedy: a resolution. Install the Sales app, before or after the core module: Install Rx Tracking (DSCSA), step 2. Nothing is lost by installing it later.

Who can fix it: Administrator (Administration: Settings).

A user has no Rx Tracking menu

What you see: the user's Inventory menu bar has no Rx Tracking dropdown, or the user has no Inventory app at all.

When: after the modules are installed, or after an administrator changed the user's access rights.

Cause: one of these:

• the user has no Rx Tracking right: only Rx Tracking User and Manager see the dropdown;
• the right was given while the user was signed in, and the user's page hasn't been reloaded since;
• the user has no Inventory right either (Rx Tracking User includes Inventory User, so this means no Rx Tracking right).

Remedy: a resolution.

1. Give the user the Rx Tracking level the job needs: Give staff the right Rx Tracking access.
2. Ask the user to reload the page, or to sign out and in again.

Which menu items each level shows: Roles and permissions.

Who can fix it: Administrator (Administration: Settings).

After an update, Apps still shows the old version

What you see: after new module folders were put on the server, the list view of Apps (list icon, top right) still shows the old number under Latest Version for the Rx Tracking modules.

When: updating the modules (Update the modules to a new version, step 1).

Cause: Latest Version shows the version of the module files the server reads. The new folders aren't on the addons path (the old ones are still read), or Odoo wasn't restarted after they were copied.

Remedy: a resolution.

1. Ask whoever runs the server to replace the folders on the addons path and restart Odoo (Update the modules to a new version, step 1).
2. Check Latest Version again, then select Upgrade on the Rx Tracking (DSCSA) card (step 3 of the same procedure). Until you do, the database keeps running the old version's screens and rules.

Who can fix it: whoever runs the server; then an administrator (Administration: Settings).

An Enterprise add-on won't install

What you see: when you select Activate on the Rx Tracking (DSCSA) - Barcode card in Apps, an Invalid Operation dialog:

You try to install module "aglow_rx_tracking_barcode" that depends on module "stock_barcode_product_expiry".
But the latter module is not available in your system.

On the Rx Tracking (DSCSA) - Suspect Product Investigations card, Activate shows no message and the card then shows Cancel Install (Known issue PF-W01-01).

When: installing an Enterprise add-on on a database that runs Odoo Community, or on a server without the Enterprise modules on its addons path.

Cause: the Barcode add-on needs Odoo Enterprise's Barcode app, and the Suspect Product add-on needs its Quality app. The two 3PL bridges need them too; they install themselves when their modules are installed.

Remedy: a workaround on Community; a resolution with Enterprise.

1. On Odoo Community, select Close. Nothing was installed. If a card shows Cancel Install, select it.
2. Use the Community procedures: Without the Barcode app and Without the Quality app.
3. With Odoo Enterprise, ask whoever runs the server to put the Enterprise modules on the addons path, then install again: Install the Enterprise add-ons.

Who can fix it: Administrator (Administration: Settings); the server's addons path: whoever runs the server.

An email or a reminder never arrived

What you see: a customer didn't get the delivery email with its DSCSA files, a portal invitation didn't arrive, or nobody got the reminder about an expiring license, an overdue discrepancy or an FDA report.

When: any time after the action that should have sent it.

Cause: one of these:

• Odoo can't send email: no outgoing mail server is set, or it refuses the messages (a neutralized copy of the database sends no email at all);
• the recipient has no email address, or a wrong one;
• the recipient handles notifications in Odoo: their Notification preference (Preferences tab of the user form) is Handle in Odoo, so reminders appear in their Odoo inbox and activities, not in email;
• the reminder has nobody to go to: a license without a Responsible, or an activity type without a default user;
• the job that sends it didn't run (A scheduled job didn't run);
• for the delivery email: the Inventory setting Email Confirmation or the DSCSA setting that attaches the files is off.

Remedy: a resolution.

1. Turn on the developer mode and go to Settings ‣ Technical ‣ Emails (in the Email section). Find the message: its status says whether it was sent, is waiting, or failed, and why.
2. For a failed message, check the server in Settings ‣ Technical ‣ Outgoing Mail Servers (in the Email section) with your IT staff.
3. Check the recipient's email address, and the user's Notification preference.
4. For reminders, check who receives them: Choose who receives the DSCSA reminder activities and No license-expiry reminder arrives.
5. For delivery emails: Send the DSCSA files with delivery confirmation emails; for a portal invitation, select Re-Invite (Give a customer portal access to its DSCSA documents).

Every email and activity the modules send, and who receives it, is listed on Every email, notification and activity the modules send.

Who can fix it: Administrator (Administration: Settings).

A scheduled job didn't run

What you see: no monthly retention export for last month, no license-expiry reminders, archive jobs staying Pending, or no FDA annual report reminder (3PL add-on).

When: after the time the job should have run.

Cause: one of these:

• the job is inactive, or its Next Execution Date is in the future;
• the database is a neutralized copy (an Odoo.sh staging database, or a restore made with Odoo's neutralize option): its scheduled jobs are switched off, and Rx Tracking also switches the off-site archive off in it;
• the Odoo server runs without its scheduler (whoever runs the server knows);
• the job ran but failed on bad data, for example a wrong reminder window in the system parameters.

Remedy: a resolution.

1. Turn on the developer mode and go to Settings ‣ Technical ‣ Scheduled Actions (in the Automation section).
2. Enter DSCSA in the search bar and press Enter. The list shows DSCSA: license expiry reminders, DSCSA: monthly retention export and DSCSA: send S3 archive queue (and, with the 3PL add-on, DSCSA 3PL: FDA annual report reminders) with their Next Execution Date and Active column.
3. Open the job, check Active and Next Execution Date, and select Run Manually to run it now (as in Check that a DSCSA job ran, and run it by hand, steps 3–5).
4. If it still doesn't run by itself, ask whoever runs the server to check that the scheduler runs for this database.

How each job works and how to tune it: Check that a DSCSA job ran, and run it by hand and Every scheduled job and what it does.

Who can fix it: Administrator (Administration: Settings).