Identify the action and installed version
The current URL-action guide names Infuse 8.4.7 or later for its documented API. Record the installed release and compare the integration with the current full article, because an older example may describe different callback fields. Do not infer the returned units from a familiar field name in a saved tutorial.
For the play action, Firecore now documents an optional starting position expressed as integer seconds, with the return carrying the last URL and position in seconds. Keep that unit explicit in any diagnostic output so a value is not silently treated as a zero-to-one progress fraction.
Interpret callback timing accurately
Multiple supplied media URLs form a temporary sequential playlist. The publisher says success is called once when playlist playback ends or when the player is closed. Those two triggering conditions mean the callback alone is not proof that every title was watched to completion.
Use the returned last item and position in the integration’s intended logic. Keep a manual close separate from a natural playlist end when reviewing an observed result. Firecore also documents a separate error callback returning failed URLs, which should not be confused with the success event’s position.
Use a small permitted comparison
For an integration you are authorised to maintain, compare two short permitted samples and a deliberate early close. Record the callback count, last item and position unit without publishing private media addresses. These are proposed checks, not tests performed by this guide.
For help, provide Infuse release, action category, expected callback policy and redacted observed fields. This evidence distinguishes per-playlist reporting, a user-closed session and an outdated callback parser. It prevents a successful return from being presented as a complete viewing record when the documented event can also occur before the playlist has finished.