Inspect the requested save behaviour
For a shortcut or integration you maintain, identify the action being sent to Infuse. The publisher documents a save action with a download parameter: zero saves the link, while one also begins downloading. Record the intended result before changing a media source or account.
The parameter applies to the entire request, including requests containing multiple URLs. A shortcut that mixes items should therefore be reviewed as one operation rather than assuming each URL silently receives a different transfer policy. Keep private source URLs out of shared screenshots or logs.
Separate action acceptance from transfer completion
The documented save success callback has no media-progress parameters. It reports the action’s successful return rather than proving a downloaded file has already finished transferring. Inspect the actual Infuse transfer state and receiving platform before relying on the item offline.
Firecore’s user download guide scopes offline file transfer to iOS and macOS and identifies where progress appears. The broader API platform list should not be used to infer that every action or download feature behaves identically on every Apple device. Use the feature-specific scope.
Verify the actual offline item
Prepare one permitted sample and confirm that a completed local copy can be opened under the intended offline conditions. Keep a saved remote link separate from that copy in your notes. If a bookmark opens while a network remains available, that observation alone does not establish local storage.
For help, provide Infuse version, receiving platform, save-action intent, download flag and observed transfer result. Redact tokens and private media locations. These details distinguish a correct link-only request, a download that is still in progress and a file that arrived but cannot play, rather than treating all successful callbacks as proof of offline readiness.